HTTP status · 3xx — redirection
307 Temporary Redirect
307 Temporary Redirect moves a request to another URL while preserving its method and body.
Key facts
| Class | 3xx — redirection |
|---|---|
| Standard | RFC 9110 §15.4.8 |
| Cacheable by default | No |
| Method handling | Preserved, including the body |
| Typical use | Temporary API or upload redirect |
What 307 means
The resource is temporarily at the URI in Location, and the client must repeat the same method and body at the new address. This is the key difference from 302: a 307 on a POST stays a POST, so the payload is not silently dropped.
307 or 308?
Both preserve the method. 307 is temporary and not cached by default; 308 is permanent and cacheable by default. Use 307 for maintenance windows, short-lived API moves or traffic shifts you intend to undo, and 308 when an endpoint has moved for good.
Frequently asked questions
What is the difference between 302 and 307?
A 302 may allow the client to change the method to GET. A 307 requires the same method and body to be replayed at the new URL.
Is 307 cached?
Not by default. Explicit cache headers can still make it cacheable.