| Previous | Next |
| HTTP_STATUS_SWITCH_PROXY | HTTP_STATUS_PERMANENT_REDIRECT |
HTTP_STATUS_TEMPORARY_REDIRECT
HTTP_STATUS_TEMPORARY_REDIRECT represents HTTP 307 Temporary Redirect. The target resource temporarily resides at the URI supplied in the Location field, while future requests should continue to use the original target URI. The redirect does not announce a permanent move.
Method preservation is the defining distinction
When a user agent automatically follows a 307 response, RFC 9110 requires it not to change the request method. A POST remains a POST, and the redirected request is expected to preserve the method semantics. This is the important difference from 302 Found, where historical compatibility permits a user agent to change POST to GET.
For diagnostics, record both request legs and compare the method, body, Location target, and authentication context. Verify that the redirected endpoint accepts the original method and body. Also check cross-origin behavior: a client can intentionally remove sensitive fields while redirecting, so a method-preserving redirect does not guarantee that every request header is copied unchanged.
References
- RFC 9110, 307 Temporary Redirect — temporary redirect semantics and method preservation.
- RFC 9110, 302 Found — historical POST-to-GET behavior that 307 avoids.
- RFC 9110, Redirection 3xx — general redirect processing and sensitive-field considerations.
Looking for a different code? Search another status or error code.