HTTP 301
From Wikipedia, the free encyclopedia
| HTTP |
| Persistence · Compression · HTTPS |
| Request methods |
| OPTIONS · GET · HEAD · POST · PUT · DELETE · TRACE · CONNECT |
| Header fields |
| Cookie · ETag · Location · Referer |
| DNT · X-Forwarded-For |
| Status codes |
| 301 Moved permanently |
| 302 Found |
| 303 See Other |
| 403 Forbidden |
| 404 Not Found |
The HTTP response status code 301 Moved Permanently is used for permanent redirection. This status code should be used with the location header. RFC 2616 states that:
- If a client has link-editing capabilities, it should update all references to the Request URI.
- The response is cachable.
- Unless the request method was HEAD, the entity should contain a small hypertext note with a hyperlink to the new URI(s).
- If the 301 status code is received in response to a request of any type other than GET or HEAD, the client must ask the user before redirecting.
- Following the HTTP 301 error code can be error 304 (Not found)
[edit] Search Engines
Google recommends using a 301 redirect to change the URL of a page as it is shown in search engine results.[1]
[edit] Notes
- ^ 301 redirects - Webmaster Tools Help - http://support.google.com/webmasters/bin/answer.py?hl=en&answer=93633
[edit] See also
 |
This World Wide Web-related article is a stub. You can help Wikipedia by expanding it. |
