303 See Other (since HTTP/1.1)
This is an educational reference page about HTTP 303 See Other. The page itself is served as 200 OK so it can be indexed as HTTP documentation.
The response to the request can be found under another URI using the GET method. When received in response to a POST (or PUT/DELETE), the client should presume that the server has received the data and should issue a new GET request to the given URI.
Specification
Registered in the IANA HTTP Status Code Registry as See Other. Defined in RFC 9110, Section 15.4.4.
Header and content rules
What RFC 9110 says about a 303 response, quoted from the RFC.
- No keyword (sender; Location): 303 is defined by the URI in Location, which the client fetches as the indirect response. RFC 9110 states no separate keyword for it. Table row
The 303 (See Other) status code indicates that the server is redirecting the user agent to a different resource, as indicated by a URI in the Location header field, which is intended to provide an indirect response to the original request. RFC 9110 §15.4.4
- No keyword (sender; content): Include a short hypertext note linking to the Location URI. RFC 9110 says "ought to", which is not a BCP 14 keyword. When: Any request except HEAD. Table row
Except for responses to a HEAD request, the representation of a 303 response ought to contain a short hypertext note with a hyperlink to the same URI reference provided in the Location header field. RFC 9110 §15.4.4
The same rules are in the response obligations table and its JSON.