| Previous | Next |
| HTTP_STATUS_MOVED | HTTP_STATUS_REDIRECT_METHOD |
HTTP_STATUS_REDIRECT
HTTP_STATUS_REDIRECT represents HTTP 302 Found. The target resource temporarily resides at the URI supplied in the Location field, and the client should continue using the original target URI for future requests. It is a temporary redirect, not a statement that the resource has permanently moved.
The method-change ambiguity is part of current HTTP semantics
Historical user-agent behavior changed POST to GET while following 302 responses. RFC 9110 preserves that compatibility by allowing a user agent to change the request method from POST to GET for a subsequent request after a 302 response. When the method and body must be preserved, HTTP 307 Temporary Redirect is the explicit alternative.
For diagnostics, inspect the Location value and capture both the original request and the redirected request. Verify whether the client changed the method, dropped the request body, or stripped credentials when crossing origins. A server that requires the same method at the new URI should not rely on every client interpreting 302 as method-preserving.
References
- RFC 9110, 302 Found — temporary redirect semantics and POST-to-GET compatibility.
- RFC 9110, 307 Temporary Redirect — method-preserving temporary redirect.
Looking for a different code? Search another status or error code.