nginx 报400 bad request 解决方法

最新推荐文章于 2025-07-01 18:11:23 发布

奥利奥泡泡

最新推荐文章于 2025-07-01 18:11:23 发布

阅读量2w

点赞数

CC 4.0 BY-SA版权

分类专栏：技术运维文章标签： nginx nginx400 bad-reques

本文链接：https://blog.youkuaiyun.com/z619193774/article/details/79829125

技术运维专栏收录该内容

16 篇文章

订阅专栏

本文介绍如何配置 Nginx 以实现 HTTP 到 HTTPS 的强制跳转，并解决由此导致的 400 Bad Request 错误。通过调整配置文件中 SSL 相关指令，确保网站能够正确地进行安全协议的转换。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

nginx 报400 bad request 解决方法

需求：要求域名强制使用https，从80端口跳转到443端口

bug出现版本：nginx 1.10.2以上版本

好多网上版本如下：

server {
    listen       443 ssl;
    server_name  xxx.xxx.com;
    root /data/wwwroot/web;

    ssl on;
    ssl_certificate /etc/nginx/certs/xxx.xxx.com/fullchain1.pem; #证书
    ssl_certificate_key /etc/nginx/certs/xxx.xxx.com/privkey1.pem; #key

    location / {
        index  index.html index.php;

        if (!-e $request_filename) {
            rewrite  ^(.*)$  /index.php/$1  last;
            break;
        }
    }

    location ~ .+\.php($|/) {
        include        php-fpm.conf;
        include        fastcgi_params;
    }

    include expires.conf;
}

server {
       listen 80;
       server_name xxx.xxx.com;
      rewrite ^/(.*) https://xxx.xxx.com/$1 permanent;
}

多次试验后发现，在某些特定的情况下，整个服务器会报出400 bad requst。

修改方法如下：

server {
    listen       443 ssl;
    server_name  xxx.xxx.com;
    root /data/wwwroot/web;

    ssl_certificate /etc/nginx/certs/xxx.xxx.com/fullchain1.pem;
    ssl_certificate_key /etc/nginx/certs/xxx.xxx.com/privkey1.pem;

    location / {
        index  index.html index.php;

        if (!-e $request_filename) {
            rewrite  ^(.*)$  /index.php/$1  last;
            break;
        }
    }

    location ~ .+\.php($|/) {
        include        php-fpm.conf;
        include        fastcgi_params;
    }

    include expires.conf;
}

server {
       listen 80;
       server_name xxx.xxx.com;
      rewrite ^/(.*) https://xxx.xxx.com/$1 permanent;
}

去掉ssl on; 即可。