301 Moved Permanently

301 moved permanently is a resource that has been requested and assigned a permanent and fresh URL. Future inquires to this newly made source is best to use a returned URL. Any users that have the ability to alter links should help in this process by editing the link and attaching the proper Request-URL to the correct references returned by a server whenever at all possible. A 301 moved permanently http response of this nature has the ability to be cached unless noted elsewhere.

If a 301 moved permanently is received back in response to the request of any type of form other than HEAD or GET, then the client is required to ask the user before redirecting. The new URL is best to be permanent and then given by the location area in the next response except when the method of request used HEAD. If the request was a HEAD response, then the entity response must contain a small text note in hyper from with a properly new URL hyperlink.

301 Moved Permanently

Client request:

GET /index.php HTTP/1.1 Host: www.servererrorcodes.com

Server response:

HTTP/1.1 301 Moved Permanently Location: http://www.servererrorcodes.com/index.php


This form of server status code, the 301 http, is typically received when a HEAD or GET request is not applicable, and the user is required not to redirect a request automatically unless it is permitted by the original user who submitted the request. It must be noted that redirecting automatically through the POST method once the request is received with a 301 moved permanently, then an existing HTTP/1.1 return request is thus changed to the GET request as shown above.

301 Http Error Code