Why does DevTools show a 307 my server did not send?
Chrome reports an Internal Redirect with status 307 when HSTS upgrades an http URL to https before any request is made. It is the browser enforcing your HSTS policy.
A temporary redirect that keeps the method and body: a POST stays a POST. 307 belongs to the 3xx redirection class and is defined in RFC 9110.
Loading the workbench.
A temporary redirect that keeps the method and body: a POST stays a POST. The code is registered with IANA and defined in RFC 9110.
Redirection: the client must take another step to finish the request. Every code from 300 to 399 shares that general meaning, so a client that does not recognise 307 must treat it like 300.
307 Temporary Redirect works like 302 with one guarantee: the client must repeat the request with the same method and body at the new URL. A POST stays a POST. Browsers also generate an internal 307 when HSTS forces an http link to https, which is why DevTools shows a 307 that your server never sent. APIs use it when an endpoint is temporarily served elsewhere, for maintenance or regional failover.
Send a Location header with the target. Make sure the target accepts the same method and body, since the client will resend them, including large uploads. If the move is permanent, switch to 308 so caches and search engines update. If a 307 in DevTools is labelled Internal Redirect, it came from HSTS in the browser, and the fix is to link to https directly.
HTTP/1.1 307 Temporary Redirect
Location: https://eu.api.example.com/v1/upload
Retry-After: 60307 is not cacheable by default: a browser or CDN stores it only when Cache-Control or Expires explicitly allows it.
To inspect a real one without sending it anywhere:
curl -i.Browse every code on the HTTP status codes page.
Elsewhere in 2http: Header decoder, Cookie decoder, Cache-Control decoder, CORS checker, User-agent parser, and all eleven lanes on the 2http home page. Part of the 2suite.io privacy-first ecosystem.
Chrome reports an Internal Redirect with status 307 when HSTS upgrades an http URL to https before any request is made. It is the browser enforcing your HSTS policy.
Both are temporary redirects. With 302 clients may change POST to GET; with 307 they must keep the original method and body.
No. 307 is a redirection response, not an error.
No. Caches store a 307 only when Cache-Control or Expires explicitly allows it.
You do not have to take our word that your headers stay here. Developer tools show every request a page makes, so you can watch this page work and confirm that nothing is sent. The check takes under a minute.
F12, or Cmd+Option+I on a Mac, and select the Network tab.Only two things can add a line to that log, and neither carries your headers. Submitting the feedback form sends the vote and comment you typed. Typing characters in a script the page has not displayed yet, such as Cyrillic or Greek, can make the browser fetch the matching font file, and that request names only the font.
2http never sends a request on your behalf: the request builder writes code for you to run, and the meta inspector reads source you paste instead of fetching a URL. The production site also sends a Content-Security-Policy header that tells your browser to refuse connections to anywhere except this site and the anonymous analytics endpoint.