【问题标题】:HTTP error body empty using NGINX as reverse proxy使用 NGINX 作为反向代理的 HTTP 错误正文为空
【发布时间】:2022-02-23 01:20:20
【问题描述】:

NGINX 代理了我的 Express NodeJS 应用程序。

在我的开发环境中,我正确地获得了错误代码和错误响应,而在生产环境中,我只获得了没有错误响应的错误代码。

但是,当我在 PowerShell 中运行失败的请求时,我确实收到了错误响应。

在生产中,API 和 APP 位于不同的子域中:

  • "api.domain.com" // Express 后端
  • "app.domain.com" // 使用 axios 的 React 应用

在开发中,所有内容都托管在同一个域中。

HTTP/2XX 请求按预期工作。

请在下面找到生产 NGINX conf(来自可用站点):

server {
    server_name api.domain.com;

    location / {

        if ($request_method = OPTIONS ) {
            add_header Content-Length 0;
            add_header Content-Type text/plain;
            add_header 'Access-Control-Allow-Origin' 'https://app.domain.com' always;
            add_header 'Access-Control-Allow-Credentials' 'true';
            add_header 'Access-Control-Allow-Methods' 'GET, POST, PATCH, PUT,OPTIONS';
            add_header 'Access-Control-Allow-Headers' 'DNT,X-CustomHeader,Keep-Alive,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type, Accept, Origin';
            return 204;
        }

        add_header 'Access-Control-Allow-Origin' 'https://app.domain.com' always;
        add_header 'Access-Control-Allow-Credentials' 'true';
        add_header 'Access-Control-Allow-Methods' 'GET, POST, PATCH, PUT,OPTIONS';
        add_header 'Access-Control-Allow-Headers' 'DNT,X-CustomHeader,Keep-Alive,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type, Accept, Origin';


        proxy_pass http://localhost:3008;
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection 'upgrade';
        proxy_set_header Host $host;
        proxy_cache_bypass $http_upgrade;
    }

    listen 443 ssl; # managed by Certbot
    ssl_certificate /etc/letsencrypt/live/api.domain.com/fullchain.pem; # managed by Certbot
    ssl_certificate_key /etc/letsencrypt/live/api.domain.com/privkey.pem; # managed by Certbot
    include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
    ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot

}
server {
    if ($host = api.domain.com) {
        return 301 https://$host$request_uri;
    } # managed by Certbot

    listen 80;
    server_name api.domain.com;
    return 404; # managed by Certbot

}

我已经测试了各种标头配置但没有成功,任何帮助将不胜感激。

【问题讨论】:

    标签: express http nginx axios nginx-reverse-proxy


    【解决方案1】:

    我缺少以下 NGINX 标头的“always”标志: add_header 'Access-Control-Allow-Credentials' 'true' 总是;

    【讨论】:

      猜你喜欢
      • 1970-01-01
      • 1970-01-01
      • 1970-01-01
      • 2011-06-08
      • 2021-06-17
      • 1970-01-01
      • 1970-01-01
      • 1970-01-01
      • 2018-05-10
      相关资源
      最近更新 更多