What 307 means
The resource is temporarily at the URL in Location. Unlike 302, the client must repeat the request exactly: same method, same body.
When servers send it
When a POST, PUT or DELETE has to be sent somewhere else for now. Browsers also show an internal 307 when HSTS upgrades an http:// link to https:// before sending anything.
Why you might see it
- A temporary redirect that keeps the method.
- HSTS: the browser itself rewrote http:// to https:// (shown as “307 Internal Redirect” in developer tools).
Using it as a developer
- Use 307 instead of 302 when the request isn’t a GET and the method matters.
- A 307 in developer tools with “Non-Authoritative-Reason: HSTS” didn’t come from your server. The browser did it because of your Strict-Transport-Security header.
If you’re visiting a website
- Nothing. Your browser follows it automatically.
Related codes
- 302 Found: The page is temporarily at the URL in the Location header.
- 308 Permanent Redirect: The page has moved for good. Repeat the same request at the new URL, with the same method and body.
- 301 Moved Permanently: The page has moved for good to the URL in the Location header.
- 303 See Other: Go and GET the URL in the Location header, typically after submitting a form.
Where it’s defined
307 Temporary Redirect is defined in RFC 9110, section 15.4.8. It’s a 3xx code, the redirection class: look somewhere else, or use the copy you already have.
Other 3xx codes
301 Moved Permanently · 302 Found · 303 See Other · 304 Not Modified · 308 Permanent Redirect
Or search them all in the HTTP status code list.