Developer
Encoders, converters & dev utilities
307 Temporary Redirect
HTTP 307 Temporary Redirect. Temporary redirect that preserves the original HTTP method and body — unlike historical 302, the client must not change POST to GET when following it. When to use it: Use for a temporary redirect of a POST/PUT where the method and body must be preserved. It is a redirection (3xx) status, so the client is expected to follow the Location header to another URL. (Reference: RFC 9110 §15.4.8.)
Temporary redirect that preserves the original HTTP method and body — unlike historical 302, the client must not change POST to GET when following it.
- When to use: Use for a temporary redirect of a POST/PUT where the method and body must be preserved.
- No fix needed — Temporary Redirect is not an error to resolve on the client side.
- Reference: RFC 9110 §15.4.8
- Category: 3xx Redirection
Frequently asked questions
What does HTTP 307 mean?
HTTP 307 Temporary Redirect: Temporary redirect that preserves the original HTTP method and body — unlike historical 302, the client must not change POST to GET when following it. It is a redirection (3xx) status, so the client is expected to follow the Location header to another URL. It is defined in RFC 9110 §15.4.8.
What is the difference between 307 and 308?
Both preserve the HTTP method and body across the redirect — the difference is permanence. 307 Temporary Redirect means the move is temporary, so clients should keep using the original URL. 308 Permanent Redirect means the move is permanent (the method-preserving equivalent of 301) and is cacheable by default. Pick 307 for a temporary move and 308 for a permanent one when the method must not change.