Example code for using Nginx to implement 301 redirect to https root domain name

Based on SEO and security considerations, a 301 redirect is required. Nginx is used for general processing below.

Achieve Results

The following addresses need to be redirected to the root domain name of https://chanvinxiao.com

• http://chanvinxiao.com (http without www)
• http://www.chanvinxiao.com (http with www)
• https://www.chanvinxiao.com (https with www)

The difference between 301 and 302

301 is a permanent redirect, 302 is a temporary redirect, the main difference is how search engines treat it

1. 301: Search engines will transfer weight and PR value
2. 302: Search engines will not perform additional processing

Now we want the search engine to think that the original address no longer exists and completely transfer it to the new address, so we use 301

http jump to https

The simplest way is to return a redirect address directly in the server, and add a 301 status code in the middle (otherwise the default is 302)

server {
 listen 80;
 return 301 https://$host$request_uri;
}

• Both return and rewrite belong to the instructions of Nginx's rewrite module. Since there is no need to modify the path here, it is more convenient to use return.
• $host and $request_uri are embedded variables of the Nginx http module. The two variables combined together are equivalent to the result of removing the http:// in the request.

www jumps to the root domain name

This only needs to be processed in https, because all http will jump to https

server {
 listen 443 ssl;
 server_name ~^(?<www>www\.)?(.+)$;
 if ( $www ) {
 return 301 https://$2$request_uri;
 }
...

• Here we use the regular expression matching function of server_name. You can enable it by adding ~ before its value. It supports PCRE syntax.
• The regular expression is used to confirm whether there is a prefix of www. and to capture the root domain name. Two variables are generated, one is the named capture variable $www and the other is the numerical capture variable $2
• If does not support the use of sequential capture variables, otherwise an error will be reported (unknown "1" variable), so ?<www> is added to assign the value of $1 to $www

Reduce the number of jumps

The above settings have met the requirements, but there is a flaw. http://www.chanvinxiao.com will first jump to https://www.chanvinxiao.com, and then jump to https://chanvinxiao.com. The second jump is definitely not as good as the first jump. So it is better to do it in one step. Modify the http configuration as follows:

server {
 listen 80;
 server_name ~^(?:www\.)?(.+)$;
 return 301 https://$1$request_uri;
}

In the server corresponding to http, change server_name to regular mode and replace $host with the captured root domain name $1
www will be directly discarded here, so there is no need to capture it. Use ?: to indicate that only grouping is done without capturing, so the root domain name behind becomes $1
The result is that regardless of whether the original domain name has www or not, it will be redirected to the https root domain name without www.

Summarize

The above configuration does not require a specific domain name, which is convenient for compatibility and portability. It uses the following features of Nginx:

• Regular expression matching for server_name
• The return instruction receives the status code and address
• $host and $request_uri embedded variables
  

This is the end of this article about using Nginx to implement 301 redirect to https root domain name. For more relevant content about Nginx 301 redirect to https root domain name, please search for previous articles on 123WORDPRESS.COM or continue to browse the following related articles. I hope everyone will support 123WORDPRESS.COM in the future!