HTTP 307 Temporary Redirect

What Does HTTP 307 Mean?

HTTP 307 Temporary Redirect works like 302 but guarantees that the request method and body will not change when following the redirect. If the original request was a POST, the redirected request will also be a POST with the same body.

HTTP 307 was introduced to address the ambiguity of 302, where browsers historically changed POST requests to GET when following redirects. With 307, the method is strictly preserved, making it safe for API redirects and form submissions.

Common uses include HSTS enforcement (redirecting HTTP to HTTPS while preserving the method), load balancing, and temporary API endpoint migrations where the request method must be maintained.

Common Causes of 307 Temporary Redirect

The resource is temporarily at a different URL, and the request method must be preserved. Common causes: HSTS HTTP-to-HTTPS redirect, temporary API endpoint relocation, load balancing.

Unlike 302, the original request method (POST, PUT, etc.) is guaranteed to be maintained in the redirect.

How to Fix 307 Temporary Redirect

HTTP 307 preserves the request method. If you need a permanent redirect, use 308 instead. If the temporary redirect is causing issues, verify the Location header URL is correct and that the destination server accepts the original HTTP method.

For HSTS redirects, 307 is the correct status code (browsers handle it automatically).

Related Status Codes

🔍 Check Your IP Address

While you're here, find out your public IP address, location, and ISP details instantly.