← Back to status codes
HTTP Status Code
307 Temporary Redirect
RedirectionThe resource is temporarily available at another URL, and the original request method should be preserved.
HTTP status code reference, response example, common causes, fixes, and related status codes.
What does HTTP 307 Temporary Redirect mean?
HTTP 307 Temporary Redirect is a status code sent by a server to indicate the result of an HTTP request.
Status codes help browsers, APIs, apps, and backend systems understand whether a request succeeded, failed, was redirected, or needs additional action.
In practice, HTTP 307 Temporary Redirect usually appears when a server responds under specific request, validation, permission, or infrastructure conditions.
Response example
HTTP/1.1 307 Temporary Redirect Location: /temporary-route
HTTP example
HTTP/1.1 307 Temporary Redirect
Relevant headers
Location
Location: /temporary-route
Common causes
- Temporary routing change
- Middleware redirect while preserving request method
How to fix it
- Check whether the redirect should really preserve method and body
- Use 302 only if method preservation is not required
Common mistakes
- Assuming the status code alone explains the full backend issue
- Ignoring related response headers that add important context
- Treating temporary errors as permanent failures
- Retrying too aggressively without checking the cause
- Debugging the frontend only when the problem is server-side
How browsers and APIs use it
Browsers, APIs, and backend services use HTTP status codes to understand the outcome of a request. Depending on the status code, an application may render content, retry a request, redirect the user, show an error, or trigger a different flow in the client or server.
Developer note
HTTP 307 is safer than 302 when you want POST to stay POST after the redirect.