Search results
Results from the WOW.Com Content Network
The HTTP response status code 303 See Other is a way to redirect web applications to a new URI, particularly after a HTTP POST has been performed, since RFC 2616 (HTTP 1.1). 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 ...
Therefore, HTTP/1.1 added status codes 303 and 307 to distinguish between the two behaviours. [1]: §15.4 303 See Other (since HTTP/1.1) 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 ...
302 found (originally "temporary redirect" in HTTP/1.0 and popularly used for CGI scripts; superseded by 303 and 307 in HTTP/1.1 but preserved for backward compatibility) 303 see other (forces a GET request to the new URL even if original request was POST) 305 use proxy (indicates that the client's requested resource is only available through a ...
The HTTP Status Code 303 See Other is to be interpreted as follows: [4]. 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.
PURLs of type 303 are used most often to redirect to metadata in a serialization format of the Resource Description Framework (RDF) and have relevance for Semantic Web and linked data content. This use of the 303 HTTP status code is conformant with the http-range-14 finding of the Technical Architecture Group of the World Wide Web Consortium.
The request/response message consists of the following: Request line, such as GET /logo.gif HTTP/1.1 or Status line, such as HTTP/1.1 200 OK,; Headers; An empty line; Optional HTTP message body data
Absolute URLs are URLs that start with a scheme [5] (e.g., http:, https:, telnet:, mailto:) [6] and conform to scheme-specific syntax and semantics. For example, the HTTP scheme-specific syntax and semantics for HTTP URLs requires a "host" (web server address) and "absolute path", with optional components of "port" and "query".
303 See Other: Used when the result of a POST or another non-idempotent request method is a resource that should be retrieved using a GET. Location header ...