See Other

3xx Redirection

Server perspective

Use 303 when the original request succeeded or was accepted, but the client should retrieve a different resource next with GET or HEAD.

•Return 303 for post/redirect/get flows after form submissions or write operations
•Use it when the redirect target is an indirect result, confirmation page, or status resource

•A short explanatory body is optional, but the redirect target should be unambiguous from Location

•Do not use 303 when the redirected request must keep the original method
•Do not confuse 303 with a generic temporary redirect; its value is the forced switch to retrieval semantics

Request:POST /checkout

Response:303 See Other with Location: /orders/123/confirmation

The server avoids duplicate purchase submission by sending the browser to a safe result page.

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 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.

Go to this other address for now, and send the exact same kind of request there.

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