HTTP 301

On the World Wide Web, HTTP 301, or 301 Moved Permanently, is the HTTP status code used for permanent redirecting. It means that links or records to this URL should be updated to the destination provided in the Location field of the server response. The 301 redirect is considered a best practice for upgrading users from HTTP to HTTPS.

RFC 2616 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.
Unless the request method was HEAD, the entity should contain a small hypertext note with a hyperlink to the new URL(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.

Examples

Client request:

Server response:

Using an .htaccess file

To fix problems with non-existing files or directories using a distributed .htaccess file:

Here is an example using a .htaccess file to redirect a non-secure URL to a secure address without the leading "www":

Static HTML

A custom directory redirect, using an index.html file:

Using programming languages

Here is an example using Perl CGI.pm:

Here is an example using a PHP redirect:

Here is one way to redirect using Express.js:

Caching server

Equivalently simple for an nginx configuration:

Search engines

Both Bing and Google recommend using a 301 redirect to change the URL of a page as it is shown in search engine results, providing that URL will permanently change and is not due to be changed again any time soon.

References