HTTP 303 – See Other
The response can be found at another URL using a GET request, commonly used after a POST.
Common use case
The Post/Redirect/Get pattern: after processing a form submission, the server redirects with 303 so a page refresh doesn't resubmit the form.
Example
HTTP/1.1 303 See Other
Location: /orders/482/confirmation
History
Introduced in HTTP/1.1 (RFC 2068, 1997) specifically to formalise the behaviour browsers were already inconsistently applying to 302.
Did you know?
Unlike 302, a 303 explicitly tells the client to always use GET for the follow-up request, regardless of the original method.