What is HTTP 307 Temporary Redirect?
The 307 Temporary Redirect status code tells clients that a resource is temporarily available at another location.
Unlike 302 Found, the client must preserve the original HTTP method when following the redirect.
Example
POST /login HTTP/1.1
HTTP/1.1 307 Temporary Redirect
Location: https://example.com/login
The client should repeat the request using POST rather than changing it to GET.
307 vs 302
Historically, implementations treated 302 responses inconsistently. The 307 response was created to guarantee method preservation.
- 302 may change POST to GET
- 307 must keep POST as POST
Common Uses
- Temporary maintenance redirects
- API routing
- Service migrations
- Traffic management
Why Does It Matter For DevOps?
DevOps engineers use 307 redirects when controlling traffic between services while preserving request behaviour.
- Reverse proxies
- API gateways
- Load balancers
- Service migrations
Summary
The 307 Temporary Redirect response temporarily redirects traffic while preserving the original HTTP method.