What it means
307 is a stricter version of 302: if the request was a POST, the redirected request must also be a POST with the same body. In Chrome DevTools you'll often see “307 Internal Redirect”. That isn't a server response; the browser itself redirects http:// to https:// because of HSTS.
Most common causes
- The server temporarily redirects a form submission or API call.
- The browser applies HSTS internally and turns an http:// request into https://.
- Maintenance or load balancing across servers.
What you can do as a visitor
- Usually there's nothing to do.
- “307 Internal Redirect” in DevTools is normal HSTS behaviour.
What the site owner or developer should do
- For permanent changes use 308 or 301.
- For APIs, check that the client follows the 307 and resends the body.
- Only enable HSTS once HTTPS works on every subdomain it covers.
Impact on SEO and Google
Google treats a 307 as a temporary redirect, the same as a 302. The internal 307 from HSTS has no SEO impact.
Frequently asked questions
What is a 307 Internal Redirect?
The browser redirects to HTTPS on its own because of HSTS, before the request ever reaches the server.
307 or 302?
307, when it matters that the method (e.g. POST) is preserved.