ErrorFindly
3073xx RedirectionLow

HTTP 307 Temporary Redirect

Defined in RFC 7231

What Does HTTP 307 Mean?

The requested resource temporarily resides at a different URL. The client must use the same HTTP method for the redirected request.

Common Causes

  1. 1HTTPS redirect preserving POST method
  2. 2Temporary API endpoint migration
  3. 3Load balancer redirecting to a different backend
  4. 4Maintenance page redirect preserving method

Impact

  • ⚠Browser redirects while preserving the original request method
  • ⚠Form data is re-sent to the new URL

Developer Fix

For web developers and application engineers

  1. 1Use 307 when POST/PUT/DELETE method must be preserved
  2. 2Prefer 307 over 302 for method-sensitive redirects
  3. 3Handle 307 by resending the original request to the new URL

Server Admin Fix

For system administrators and DevOps engineers

  1. 1Use 307 for HSTS redirects (HTTP to HTTPS)
  2. 2Configure proper Location headers
  3. 3Monitor for redirect loops

Frequently Asked Questions

What's the difference between 307 and 302?
307 guarantees the request method won't change during the redirect. 302 technically allows the method to change (though modern browsers usually don't). Use 307 when method preservation is critical.
When should I use 307 vs 308?
Use 307 for temporary redirects where the method must be preserved. Use 308 for permanent redirects where the method must be preserved. Think of 307/308 as method-safe versions of 302/301.

Related HTTP Status Codes

302Found308Permanent Redirect301Moved Permanently

About the Author

Web Infrastructure Team

Verified against official RFC specifications and real-world server configurations. HTTP status code behavior confirmed across Apache, Nginx, and Cloudflare.