Temporary Redirect

3xx Redirection

Server perspective

Use 307 when the redirect is temporary and the follow-up request must keep the same method and body.

•Return 307 for temporary API or infrastructure moves that cannot tolerate method rewriting
•Choose 307 over 302 when non-GET behavior must remain exact

•Include a Location header with the temporary URI
•Make sure the target endpoint can safely handle the same method and request body

•A body is optional, but the redirect target and temporary nature should be clear

•Do not use 307 if you actually want the redirected request to switch to GET
•Do not mark a long-term move as temporary if clients should update their stored URIs

Request:PATCH /api/orders/123

Response:307 Temporary Redirect with Location: /maintenance/orders/123

The server preserves request semantics while moving traffic for a limited time.

There are several valid versions of this thing, and the server is asking you to pick one.

This moved for good. Start using the new address from now on.

Go somewhere else for now, but don’t assume this new address is the permanent one.

You submitted something successfully. Now go fetch this other page to see the result.

You already have the latest version! The thing you're asking for hasn't changed since you last got it.

This is an old HTTP idea that said, 'Use this proxy instead,' but modern systems should not rely on it.

This number exists in the HTTP list, but it does not mean anything you should use in a real app today.

This moved for good, and you should keep using the same kind of request when you switch to the new address.