Search results
Results From The WOW.Com Content Network
An HTTP response with this status code will additionally provide a URL in the header field Location. This is an invitation to the user agent (e.g. a web browser) to make a second, otherwise identical, request to the new URL specified in the location field. The end result is a redirection to the new URL.
The new URL should be provided in the Location field, included with the response. The 301 redirect is considered a best practice for upgrading users from HTTP to HTTPS. RFC 2616 [1] states that: If a client has link-editing capabilities, it should update all references to the Request URL. The response is cacheable unless indicated otherwise.
The only redirect category templates that should be applied are {{R from statistical redirect}} and, if the redirect is in mainspace, {{R unprintworthy}}. These should be applied within the {{ Redirect category shell }} to ensure protection levels are detected and categorized appropriately.
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. A user agent may automatically redirect a request.
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 common media type parameter is charset, specifying the character set of the media type, where the value is from the IANA list of character set names. [6] If one is not specified, the media type of the data URI is assumed to be text/plain;charset=US-ASCII .
URL hijacking is an off-domain redirect technique [3] that exploited the nature of the search engine's handling for temporary redirects. If a temporary redirect is encountered, search engines have to decide whether they assign the ranking value to the URL that initializes the redirect or to the redirect target URL.
This takes you to the redirect page itself. (The URL for accessing a redirect page without following the redirect contains the query parameter redirect=no.) Another way to get to a redirect page is to go to the target page, and click "What links here" (in the toolbox on the left of the page).