Search results
Results from the WOW.Com Content Network
This class of status code indicates the client must take additional action to complete the request. Many of these status codes are used in URL redirection. [2]A user agent may carry out the additional action with no user interaction only if the method used in the second request is GET or HEAD.
The HTTP response status code 302 Found is a common way of performing URL redirection. The HTTP/1.0 specification (RFC 1945) initially defined this code, and gave it the description phrase "Moved Temporarily" rather than "Found". An HTTP response with this status code will additionally provide a URL in the header field Location.
Moved temporarily; Moved permanently; or; Processed a request, e.g. a POSTed form, and is providing the result of that request at a different URI; To provide information about the location of a newly created resource. In this circumstance, the Location header should be sent with an HTTP status code of 201 or 202. [1]
302 Moved Temporarily The client should try at the address in the Contact field. If an Expires field is present, the client may cache the result for that period of time. [1]: §21.3.3 305 Use Proxy The Contact field details a proxy that must be used to access the requested destination. [1]: §21.3.4 380 Alternative Service
Nginx has an integrated http rewrite module, [10] which can be used to perform advanced URL processing and even web-page generation (with the return directive). An example of such advanced use of the rewrite module is mdoc.su, which implements a deterministic URL shortening service entirely with the help of nginx configuration language alone ...
it has no HTTP headers and lacks many other features that nowadays are required for minimal security reasons; it has not been widespread since 1999..2000 (because of HTTP/1.0 and HTTP/1.1) and is commonly used only by some very old network hardware, i.e. routers , etc.
If an entity is temporarily unavailable, this instructs the client to try again later. Value could be a specified period of time (in seconds) or a HTTP-date. [56] Example 1: Retry-After: 120; Example 2: Retry-After: Fri, 07 Nov 2014 23:59:59 GMT; Permanent RFC 9110: Server: A name for the server: Server: Apache/2.4.1 (Unix) Permanent RFC 9110 ...
For version 1.1 of the HTTP protocol, the chunked transfer mechanism is considered to be always and anyway acceptable, even if not listed in the TE (transfer encoding) request header field, and when used with other transfer mechanisms, should always be applied last to the transferred data and never more than one time.