What 303 means
Go and fetch a different URL, given in Location, with a GET. It doesn’t mean the original resource moved. It points to a result page.
When servers send it
After a form POST, so refreshing the result page doesn’t submit the form again. This is the Post/Redirect/Get pattern.
Why you might see it
- An app following Post/Redirect/Get.
- An async job’s status URL redirecting to the finished result.
Using it as a developer
- Use 303 after any POST that changes data and then shows a page. It stops the “Resubmit the form?” warning on refresh.
- The client always switches to GET (or HEAD), whatever the original method.
If you’re visiting a website
- Nothing. Your browser follows it automatically.
Related codes
- 302 Found: The page is temporarily at the URL in the Location header.
- 307 Temporary Redirect: The page is temporarily at the URL in the Location header. Repeat the same request there, with the same method and body.
- 202 Accepted: The request has been accepted for processing later, but it hasn’t been done yet.
- 201 Created: The request worked and created something new, usually found at the URL in the Location header.
Where it’s defined
303 See Other is defined in RFC 9110, section 15.4.4. It’s a 3xx code, the redirection class: look somewhere else, or use the copy you already have.
Other 3xx codes
301 Moved Permanently · 302 Found · 304 Not Modified · 307 Temporary Redirect · 308 Permanent Redirect
Or search them all in the HTTP status code list.