- Home
- Tools
- Developer Tools
- HTTP Status Codes
- 303 See Other
303 See Other
The result of this request is at another address, to be fetched with a GET. The standard answer to a submitted form.
- Class
- 3xx Redirection. The client has to take another step to finish the request, usually fetching a different address.
- Defined in
- RFC 9110
What it looks like
HTTP/1.1 303 See Other Location: /orders/1042
When a server sends it
After a POST that worked: the server stores the order or the comment and sends the browser on to a page that shows it. This pattern (post, redirect, get) keeps the reload and back buttons of the browser from sending the form a second time.
What to do with it
Clients fetch the address in Location with a GET, whatever the method of the first request was. Nothing else is needed.
If you build forms, answer a successful POST with a 303 and not with the result page itself. The redirect is never stored as a replacement for the original address.
Not to be confused with
| 302 Found | In practice the same for a POST, but the standard leaves the method open. |
|---|---|
| 307 Temporary Redirect | The opposite: the method must not change. |
| 201 Created | The answer of an API to a POST that made something: no redirect, the new address is in Location. |
How Google treats it
Google follows a 303 and treats it like a 302, as a weak signal.
All codes are on the list of HTTP status codes, which can be searched by number and by word.