Nginx domain name access judgment

Little scum · Posted on 12/7/2015 7:24:30 PM

The requirements are as follows:

1. Access to non-www.abc.com domain names, return 403 to prevent malicious parsing.

Even if someone else's domain is bound to your host's IP, they won't be able to access your site, and if a user accesses his domain name, the user's browser will return a 403 error instead of jumping out of your site.
2. When the abc.com domain name is accessed, the automatic 301 is rewritten to www.abc.com, increasing the SEO weight...

Increase domain authority
Optimization of web page inclusion
It is conducive to the delivery of web page PR
It can promote search engine optimization results
Be friendly to user experience
3. The above two needs coexist.

1. Access to non-www.abc.com domain names, return 403 to prevent malicious parsing.

server {
      listen    80;
      server_name  abc.com www.abc.com;
if ( $host != 'www.abc.com' ){
      return 403;
      }
2. When a abc.com domain name is accessed, the 301 is automatically rewritten to www.abc.com.

server {
      listen    80;
      server_name  abc.com www.abc.com;
if ( $host = 'abc.com' ){
      rewrite http://abc.com/(.*) http://www.abc.com/$1 permanent;
      }
3. Non-www.abc.com domain name access, return 403 error, when abc.com domain name access, automatically rewrite 301 to www.abc.com.

server {
      listen    80;
      server_name  www.abc.com abc.com;

if ( $host = 'abc.com' ){
      rewrite http://abc.com/(.*) http://www.abc.com/$1 permanent;
   }

if ( $host != 'www.abc.com' ){
      return 403;
      #rewrite ^/(.*)$ http://www.abc.com/$1 permanent;

   }

[Web] Nginx domain name access judgment

Related Posts