|Response status codes|
|Security access control methods|
According to RFC 7231, which obsoletes RFC 2616, "A 303 response to a GET request indicates that the origin server does not have a representation of the target resource that can be transferred by the server over HTTP. However, the Location field value refers to a resource that is descriptive of the target resource, such that making a retrieval request on that other resource might result in a representation that is useful to recipients without implying that it represents the original target resource."
This status code should be used with the location header, as described below. If a server responds to a POST or other non-idempotent request with a 303 See Other response and a value for the location header, the client is expected to obtain the resource mentioned in the location header using the GET method; to trigger a request to the target resource using the same method, the server is expected to provide a 307 Temporary Redirect response.
303 See Other has been proposed as one way of responding to a request for a
http://www.example.com/id/aliceidentifies a person, Alice, then it would be inappropriate for a server to respond to a GET request with 200 OK, as the server could not deliver Alice herself. Instead the server would issue a 303 See Other response which redirected to a separate URI providing a description of the person Alice.
303 See Other can be used for other purposes. For example, when building a
POST / HTTP/1.1 Host: www.google.com
HTTP/1.1 303 See Other Location: http://bing.com/?toWww=1&redig=3A3DCA836C824D0FB1A4643A56878631
- RFC 1945 (HTTP 1.0)
- RFC 7231 (HTTP 1.1)
- Hypertext Transfer Protocol
- List of HTTP status codes
- HTTP 301 (Permanent redirect)
- ^ "Cool URIs for the Semantic Web: Hash URIs". W3C Interest Group Note. 2008-12-03.
- ISBN 9780596801687.