search
HomeOperation and MaintenanceNginxUse nginx to implement 301 jump to the root domain name of https

Use nginx to implement 301 jump to the root domain name of https

基于SEO和安全性的考虑,现在需要进行 301 跳转。以下方法使用 Nginx 作通用处理。

(推荐教程:nginx教程

实现结果

需要将以下地址都统一跳转到 https 的根域名 https://chanvinxiao.com

http://chanvinxiao.com (不带 www 的 http)
http://www.chanvinxiao.com (带 www 的 http)
https://www.chanvinxiao.com (带 www 的 https)

301 与 302 的区别

301 是永久重定向,302 是临时跳转,主要的区别在于搜索引擎对此的对待方式

301:搜索引擎会将权重和 PR 值进行转移302:搜索引擎不会进行额外处理

现在是希望搜索引擎认为原地址已经不存在了,完全转移到新地址,所以使用 301

http 跳转到 https

最简单的方法是直接在 sever 中返回一个重定向的地址,中间再加上 301 状态码(否则默认为 302)

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

return 和 rewrite 都属于 Nginx 的重写模块的指令,因为这里不需要对路径进行修改,所以用 return 会比较方便$host 和 $request_uri 都是 Nginx http 模块的嵌入变量,两个变量合并一起就相当于把请求的 http:// 去掉的结果

www 跳转到根域名

这个只需在 https 中作处理,因为所有 http 都跳转到 https 了

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

这里利用了 server_name 的正则匹配功能,在其值前增加 ~ 即可启用,支持 PCRE 语法使用正则是为了确认是否有前缀 www. 以及捕获根域名,生成两个变量,一个是具名捕获变量 $www ,另一个是数值捕获变量 $2if 里面不支持使用数值捕获变量,否则会报错( unknown "1" variable),所以增加了 ? 将 $1 的值赋给了 $www

减少跳转次数

以上设置已经满足了实现结果,但是有一点瑕疵,就是 http://www.chanvinxiao.com 会先跳转到 https://www.chanvinxiao.com, 再跳转到 https://chanvinxiao.com ,进行二次跳转肯定是不如只需跳转一次的,所以最好让其直接一步到位,修改 http 的配置如下:

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

在 http 对应的 sever 中,把 server_name 也改为正则模式,并将 $host 用捕获的根域名 $1 取代www 在这里会直接弃掉,所以不需要捕获,使用 ?: 标示实现只分组不捕获,于是后面的根域名就成了 $1这样的结果是不管原来是否带 www,都统一跳转到不带 www 的 https 根域名

总结

以上配置中不需指定特定域名,可方便兼容和移植,使用了 Nginx 的以下特性:

server_name 的正则匹配

return 指令接收状态码和地址

$host 和 $request_uri 嵌入变量

The above is the detailed content of Use nginx to implement 301 jump to the root domain name of https. For more information, please follow other related articles on the PHP Chinese website!

Statement
This article is reproduced at:掘金. If there is any infringement, please contact admin@php.cn delete
Using NGINX Unit: Deploying and Managing ApplicationsUsing NGINX Unit: Deploying and Managing ApplicationsApr 22, 2025 am 12:06 AM

NGINXUnit can be used to deploy and manage applications in multiple languages. 1) Install NGINXUnit. 2) Configure it to run different types of applications such as Python and PHP. 3) Use its dynamic configuration function for application management. Through these steps, you can efficiently deploy and manage applications and improve project efficiency.

NGINX vs. Apache: A Comparative Analysis of Web ServersNGINX vs. Apache: A Comparative Analysis of Web ServersApr 21, 2025 am 12:08 AM

NGINX is more suitable for handling high concurrent connections, while Apache is more suitable for scenarios where complex configurations and module extensions are required. 1.NGINX is known for its high performance and low resource consumption, and is suitable for high concurrency. 2.Apache is known for its stability and rich module extensions, which are suitable for complex configuration needs.

NGINX Unit's Advantages: Flexibility and PerformanceNGINX Unit's Advantages: Flexibility and PerformanceApr 20, 2025 am 12:07 AM

NGINXUnit improves application flexibility and performance with its dynamic configuration and high-performance architecture. 1. Dynamic configuration allows the application configuration to be adjusted without restarting the server. 2. High performance is reflected in event-driven and non-blocking architectures and multi-process models, and can efficiently handle concurrent connections and utilize multi-core CPUs.

NGINX vs. Apache: Performance, Scalability, and EfficiencyNGINX vs. Apache: Performance, Scalability, and EfficiencyApr 19, 2025 am 12:05 AM

NGINX and Apache are both powerful web servers, each with unique advantages and disadvantages in terms of performance, scalability and efficiency. 1) NGINX performs well when handling static content and reverse proxying, suitable for high concurrency scenarios. 2) Apache performs better when processing dynamic content and is suitable for projects that require rich module support. The selection of a server should be decided based on project requirements and scenarios.

The Ultimate Showdown: NGINX vs. ApacheThe Ultimate Showdown: NGINX vs. ApacheApr 18, 2025 am 12:02 AM

NGINX is suitable for handling high concurrent requests, while Apache is suitable for scenarios where complex configurations and functional extensions are required. 1.NGINX adopts an event-driven, non-blocking architecture, and is suitable for high concurrency environments. 2. Apache adopts process or thread model to provide a rich module ecosystem that is suitable for complex configuration needs.

NGINX in Action: Examples and Real-World ApplicationsNGINX in Action: Examples and Real-World ApplicationsApr 17, 2025 am 12:18 AM

NGINX can be used to improve website performance, security, and scalability. 1) As a reverse proxy and load balancer, NGINX can optimize back-end services and share traffic. 2) Through event-driven and asynchronous architecture, NGINX efficiently handles high concurrent connections. 3) Configuration files allow flexible definition of rules, such as static file service and load balancing. 4) Optimization suggestions include enabling Gzip compression, using cache and tuning the worker process.

NGINX Unit: Supporting Different Programming LanguagesNGINX Unit: Supporting Different Programming LanguagesApr 16, 2025 am 12:15 AM

NGINXUnit supports multiple programming languages ​​and is implemented through modular design. 1. Loading language module: Load the corresponding module according to the configuration file. 2. Application startup: Execute application code when the calling language runs. 3. Request processing: forward the request to the application instance. 4. Response return: Return the processed response to the client.

Choosing Between NGINX and Apache: The Right Fit for Your NeedsChoosing Between NGINX and Apache: The Right Fit for Your NeedsApr 15, 2025 am 12:04 AM

NGINX and Apache have their own advantages and disadvantages and are suitable for different scenarios. 1.NGINX is suitable for high concurrency and low resource consumption scenarios. 2. Apache is suitable for scenarios where complex configurations and rich modules are required. By comparing their core features, performance differences, and best practices, you can help you choose the server software that best suits your needs.

See all articles

Hot AI Tools

Undresser.AI Undress

Undresser.AI Undress

AI-powered app for creating realistic nude photos

AI Clothes Remover

AI Clothes Remover

Online AI tool for removing clothes from photos.

Undress AI Tool

Undress AI Tool

Undress images for free

Clothoff.io

Clothoff.io

AI clothes remover

Video Face Swap

Video Face Swap

Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Tools

SecLists

SecLists

SecLists is the ultimate security tester's companion. It is a collection of various types of lists that are frequently used during security assessments, all in one place. SecLists helps make security testing more efficient and productive by conveniently providing all the lists a security tester might need. List types include usernames, passwords, URLs, fuzzing payloads, sensitive data patterns, web shells, and more. The tester can simply pull this repository onto a new test machine and he will have access to every type of list he needs.

WebStorm Mac version

WebStorm Mac version

Useful JavaScript development tools

Atom editor mac version download

Atom editor mac version download

The most popular open source editor

EditPlus Chinese cracked version

EditPlus Chinese cracked version

Small size, syntax highlighting, does not support code prompt function

DVWA

DVWA

Damn Vulnerable Web App (DVWA) is a PHP/MySQL web application that is very vulnerable. Its main goals are to be an aid for security professionals to test their skills and tools in a legal environment, to help web developers better understand the process of securing web applications, and to help teachers/students teach/learn in a classroom environment Web application security. The goal of DVWA is to practice some of the most common web vulnerabilities through a simple and straightforward interface, with varying degrees of difficulty. Please note that this software