HTTP 302 — Found
HTTP 302 sends the client to the Location URL for now, explicitly leaving the old one valid. Despite the historical confusion around method rewriting, it remains the common choice for short-lived redirects.
When 302 shows up
- Login flows that bounce through a session provider and back.
- Temporary redirects during campaigns or maintenance windows.
Mocking a 302 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": "/login/return",
"status": 302,
"delay": 140,
"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 302 mean?
The resource is temporarily at a different URL. Keep using the original one for future requests — the move is not permanent.
How can I test a 302 response without a real backend?
Define a mock rule with the method and path your client requests and set the status to 302. The example configuration above returns this response after the listed delay, so the client exercises its 302 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.