Temporary Redirect — the resource temporarily resides at a different location
What 307 Means
The 307 error on the HTTP Status-Codes indicates temporary redirect — the resource temporarily resides at a different location. This typically occurs due to form submission redirected to a different processing endpoint.
A 307 Temporary Redirect is the strict successor to the 302 code. It guarantees that the HTTP method used by the client will remain entirely unchanged when following the redirect to the new Location URL.
Technical Background
The creation of the 307 status resolved a historical ambiguity in early web standards. Originally, many browsers incorrectly changed POST requests into GET requests when following a 302 redirect, breaking forms and payment data transmissions in the process.
A 307 explicitly outlaws this behavior. When a client receives a 307 in response to a POST request, it is obligated to reuse the POST method and the exact original body payload when requesting the temporary new address.
Because of this strict method guarantee, APIs and secure transactional systems prefer 307 over 302. It ensures that sensitive operations are not accidentally converted into plain retrieval requests.
Common Causes
- Form submission redirected to a different processing endpoint
- API versioning routing where the method must be preserved
- Internal geographic routing prior to serving a resource
- Strict application frameworks enforcing modern standards
Typical Scenarios
- An application temporarily redirects a POST form submission to a fallback server
- A strict API forces an incoming PUT request to hit an alternative data center
- A modern framework defaults to 307 instead of 302 to maintain security expectations
What to Know
A 307 guarantees mechanical predictably during a temporary shift. If an application suddenly starts failing on a 307 redirect, the client library is likely failing to retransmit the initial request payload properly to the newly specified endpoint.
Frequently Asked Questions
Common questions about HTTP 307 error
Both indicate a temporary redirect. However, a 302 historically caused some clients to change POST requests to GET. A 307 strictly requires the client to keep the original method.
Yes, especially for API endpoints or form submissions. A 307 is much safer when you must guarantee that the HTTP method and request body are preserved across the redirect.
Like a 302, search engines treat a 307 as a temporary move. They will follow the redirect but continue to index the original URL.