HTTP 307 — Temporary Redirect
HTTP 307 moves the client to another URL for now with one guarantee 302 never quite made: the request method and body must be replayed unchanged. A POST stays a POST at the new location.
When 307 shows up
- Temporary redirects that must not downgrade a POST to GET.
- Routing around a failing node while preserving the exact request shape.
Mocking a 307 response
A response with this status can be faked end to end with a local mock rule — no backend changes needed. The configuration below mirrors the rule fields the ApiSimul editor uses (method, path, status, delay in milliseconds, response body):
{
"method": "GET",
"path": "/api/submit",
"status": 307,
"delay": 170,
"enabled": true,
"body": null
}Dynamic placeholders such as {{random.name}}, {{string.uuid}} or {{number.int 1 100}} can appear inside the body to vary each response, which keeps client-side list rendering and retry logic honest during development.
Frequently asked questions
What does HTTP 307 mean?
The resource is temporarily elsewhere and the request must be repeated there with the same method and body. The original URL remains the one to use later.
How can I test a 307 response without a real backend?
Define a mock rule with the method and path your client requests and set the status to 307. The example configuration above returns this response after the listed delay, so the client exercises its 307 handling exactly as it would against a live server.
Related status codes
Need the response in your own project? Spin up rules for any status with the ApiSimul mock server, or browse every status code page.