Search results
Results from the WOW.Com Content Network
For example, a POST request should be repeated using another POST request. 308 Permanent Redirect This and all future requests should be directed to the given URI. 308 parallels the behavior of 301, but does not allow the HTTP method to change. So, for example, submitting a form to a permanently redirected resource may continue smoothly.
302 Found: Unlike a 301, a 302 status code indicates a temporary redirect.Search engines might not pass the SEO value to the new URL. [5]307 Temporary Redirect: Like 302, but guarantees that the method and the body will not be changed when the redirected request is made.
[14] [15] A timeout of zero seconds effects an immediate redirect. This is treated like a 301 permanent redirect by Google, allowing transfer of PageRank to the target page. [16] This is an example of a simple HTML document that uses this technique:
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]
An alternative is to send an HTTP redirection status code, such as HTTP 301 or 302. It is the preferred way to redirect a user agent to a different page. This can be achieved by a special rule in the Web server or by means of a simple script on the Web server.
Diagram of a double POST problem encountered in user agents. Diagram of the double POST problem above being solved by PRG. Post/Redirect/Get (PRG) is a web development design pattern that lets the page shown after a form submission be reloaded, shared, or bookmarked without ill effects, such as submitting the form another time.
A specific flow to a user agent has failed, although other flows may succeed. This response is intended for use between proxy devices, and should not be seen by an endpoint (and if it is seen by one, should be treated as a 400 Bad Request response). [16]: §11.5 433 Anonymity Disallowed The request has been rejected because it was anonymous. [17]
A client request (consisting in this case of the request line and a few headers that can be reduced to only the "Host: hostname" header) is followed by a blank line, so that the request ends with a double end of line, each in the form of a carriage return followed by a line feed.