307 Temporary Redirect means the target resource is temporarily at the URL in the Location header, and the client must not change the request method when it follows the redirect. A POST stays a POST with the same body, and a PUT stays a PUT. Future requests should still go to the original URL. A 307 is not cacheable by default.
HTTP/1.1 added 307 to remove the ambiguity of 302 Found, which browsers follow with GET after a POST. Use it for temporary redirects of API endpoints, uploads and form posts, or wherever the method must be preserved.
In browser developer tools you may see 307 Internal Redirect after typing an http:// address of a site that uses HSTS. That redirect is generated by the browser itself from its HSTS list and never reached the server; the server's own redirect may well be a 301. A server-side check such as TrueURL's HTTPS Redirect Checker shows what the server actually sends.
Example response
HTTP/1.1 307 Temporary Redirect
Date: Fri, 06 Nov 2026 10:15:32 GMT
Location: https://eu.api.example.com/v1/upload
Cache-Control: no-store
Content-Length: 0SEO and redirect checking
Google treats 307 like 302: a temporary redirect and a weak canonical signal, so the original URL usually stays indexed. That is right for temporary situations; for permanent moves use 308 or 301. Some frameworks produce 307 by default. Next.js, for example, uses 307 for redirects with permanent: false and 308 for permanent: true, so check which one your configuration generates.
Common causes and use cases
- An API or upload endpoint moved temporarily, and
POSTbodies must survive the redirect. - Maintenance, load balancing or regional routing sends requests elsewhere for a while.
- A framework's default temporary redirect, such as Next.js with
permanent: falseorRedirectResponsein Starlette and FastAPI. - The "307 Internal Redirect" for HSTS in browser developer tools, which comes from the browser, not from the server.