使用Nginx代理后CORS Header丢失问题求助

API 探路者

2026-7-4

解决Nginx代理Gin后端时CORS头丢失问题

问题背景

后端采用Go+Gin框架开发，通过Gin的cors中间件配置CORS规则并部署在Docker中。直接访问后端端口时，前端可正常接收CORS响应头；但通过Nginx部署前端并将/api请求代理到后端时，浏览器提示CORS错误，响应头中无任何CORS相关字段，使用浏览器插件绕过CORS限制后功能正常，说明代理配置本身有效。

Gin后端CORS配置

r.Use(cors.New(cors.Config{
        AllowAllOrigins:  true,
        AllowMethods:     []string{"GET", "POST", "PUT", "DELETE", "OPTIONS", "HEAD"},
        AllowHeaders:     []string{"Origin", "Content-Length", "Content-Type", "Authorization"},
        AllowCredentials: true,
        MaxAge:           12 * time.Hour,
    }))

浏览器错误提示

Access to XMLHttpRequest at 'mywebsite/api' from origin 'mywebsite' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.

Nginx配置

# Generated by nginxconfig.io
# See nginxconfig.txt for the configuration share link

user nginx;
pid /var/run/nginx.pid;
worker_processes auto;
worker_rlimit_nofile 65535;

# Load modules
include /etc/nginx/modules-enabled/*.conf;

events {
    multi_accept on;
    worker_connections 65535;
}

http {
    charset utf-8;
    sendfile on;
    tcp_nopush on;
    tcp_nodelay on;
    server_tokens off;
    log_not_found off;
    types_hash_max_size 2048;
    types_hash_bucket_size 64;
    client_max_body_size 16M;

    # MIME
    include mime.types;
    default_type application/octet-stream;

    # Logging
    access_log off;
    error_log /var/log/nginx/error.log warn;

    # Limits
    limit_req_log_level warn;
    limit_req_zone $binary_remote_addr zone=login:10m rate=60r/m;

    # SSL
    ssl_session_timeout 1d;
    ssl_session_cache shared:SSL:10m;
    ssl_session_tickets off;

    # Mozilla Modern configuration
    ssl_protocols TLSv1.3;

    # OCSP Stapling
    ssl_stapling on;
    ssl_stapling_verify on;
    resolver 114.114.114.114 valid=60s;
    resolver_timeout 2s;

    # Connection header for WebSocket reverse proxy
    map $http_upgrade $connection_upgrade {
        default upgrade;
        "" close;
    }

    map $remote_addr $proxy_forwarded_elem {

        # IPv4 addresses can be sent as-is
        ~^[0-9.]+$ "for=$remote_addr";

        # IPv6 addresses need to be bracketed and quoted
        ~^[0-9A-Fa-f:.]+$ "for=\"[$remote_addr]\"";

        # Unix domain socket names cannot be represented in RFC 7239 syntax
        default "for=unknown";
    }

    map $http_forwarded $proxy_add_forwarded {

        # If the incoming Forwarded header is syntactically valid, append to it
        "~^(,[ \t]*)*([!#$%&'*+.^_`|~0-9A-Za-z-]+=([!#$%&'*+.^_`|~0-9A-Za-z-]+|\"([\t \x21\x23-\x5B\x5D-\x7E\x80-\xFF]|\\[\t \x21-\x7E\x80-\xFF])*\"))?(;([!#$%&'*+.^_`|~0-9A-Za-z-]+=([!#$%&'*+.^_`|~0-9A-Za-z-]+|\"([\t \x21\x23-\x5B\x5D-\x7E\x80-\xFF]|\\[\t \x21-\x7E\x80-\xFF])*\"))?)*([ \t]*,([ \t]*([!#$%&'*+.^_`|~0-9A-Za-z-]+=([!#$%&'*+.^_`|~0-9A-Za-z-]+|\"([\t \x21\x23-\x5B\x5D-\x7E\x80-\xFF]|\\[\t \x21-\x7E\x80-\xFF])*\"))?(;([!#$%&'*+.^_`|~0-9A-Za-z-]+=([!#$%&'*+.^_`|~0-9A-Za-z-]+|\"([\t \x21\x23-\x5B\x5D-\x7E\x80-\xFF]|\\[\t \x21-\x7E\x80-\xFF])*\"))?)*)?)*$" "$http_forwarded, $proxy_forwarded_elem";

        # Otherwise, replace it
        default "$proxy_forwarded_elem";
    }

    # Load configs
    include /etc/nginx/conf.d/*.conf;

    # mywebsite
    server {
        listen 443 ssl http2;
        listen [::]:443 ssl http2;
        server_name mywebsite;
        root /var/www/mywebsite.site/public;

        # SSL
        ssl_certificate /etc/nginx/ssl/mywebsite.crt;
        ssl_certificate_key /etc/nginx/ssl/mywebsite.key;

        # security headers
        add_header X-XSS-Protection "1; mode=block" always;
        add_header X-Content-Type-Options "nosniff" always;
        add_header Referrer-Policy "no-referrer-when-downgrade" always;
        add_header Content-Security-Policy "default-src 'self' http: https: ws: wss: data: blob: 'unsafe-inline'; frame-ancestors 'self';" always;
        add_header Permissions-Policy "interest-cohort=()" always;
        add_header Strict-Transport-Security "max-age=31536000; includeSubDomains" always;

        # . files
        location ~ /\.(?!well-known) {
            deny all;
        }

        # logging
        error_log /var/log/nginx/error.log warn;

        # reverse proxy
        location /api/ {
            proxy_pass http://172.17.0.2:8080;
            proxy_set_header Host $host;
            proxy_http_version 1.1;
            proxy_cache_bypass $http_upgrade;

            # Proxy SSL
            proxy_ssl_server_name on;

            # Proxy headers
            proxy_set_header Upgrade $http_upgrade;
            proxy_set_header Connection $connection_upgrade;
            proxy_set_header X-Real-IP $remote_addr;
            proxy_set_header Forwarded $proxy_add_forwarded;
            proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
            proxy_set_header X-Forwarded-Proto $scheme;
            proxy_set_header X-Forwarded-Host $host;
            proxy_set_header X-Forwarded-Port $server_port;

            # Proxy timeouts
            proxy_connect_timeout 60s;
            proxy_send_timeout 60s;
            proxy_read_timeout 60s;
        }


        # favicon.ico
        location = /favicon.ico {
            log_not_found off;
        }

        # robots.txt
        location = /robots.txt {
            log_not_found off;
        }

        # assets, media
        location ~* \.(?:css(\.map)?|js(\.map)?|jpe?g|png|gif|ico|cur|heic|webp|tiff?|mp3|m4a|aac|ogg|midi?|wav|mp4|mov|webm|mpe?g|avi|ogv|flv|wmv)$ {
            expires 7d;
        }

        # svg, fonts
        location ~* \.(?:svgz?|ttf|ttc|otf|eot|woff2?)$ {
            add_header Access-Control-Allow-Origin "*";
            expires 7d;
        }

        # gzip
        gzip on;
        gzip_vary on;
        gzip_proxied any;
        gzip_comp_level 6;
        gzip_types text/plain text/css text/xml application/json application/javascript application/rss+xml application/atom+xml image/svg+xml;
    }

    # non-www, subdomains redirect
    server {
        listen 443 ssl http2;
        listen [::]:443 ssl http2;
        server_name .mywebsite;

        # SSL
        ssl_certificate /etc/nginx/ssl/mywebsite.crt;
        ssl_certificate_key /etc/nginx/ssl/mywebsite.key;
        return 301 https://mysite$request_uri;
    }

    # HTTP redirect
    server {
        listen 80;
        listen [::]:80;
        server_name .mywebsite;
        return 301 https://www.mywebsite$request_uri;
    }
}

已尝试的无效方案

在Nginx配置中添加不同规则的CORS头
在Gin中手动设置CORS头
移除后端CORS配置，仅用Nginx处理CORS

解决方案

核心问题分析

代理路径不匹配：当前proxy_pass末尾未加斜杠，导致/api/xxx被转发为http://172.17.0.2:8080api/xxx，后端路由无法匹配，返回404，此时Gin的CORS中间件不会触发。
Nginx头覆盖问题：add_header默认仅在2xx/3xx响应中生效，OPTIONS预检请求若返回非2xx状态，头信息会丢失；同时前后端CORS配置冲突可能导致头被覆盖。
Docker网络稳定性：使用固定IP代理后端容器易因容器重启导致IP变化，引发连接问题。

修复步骤

修正Nginx代理路径
在proxy_pass末尾添加斜杠，确保路径正确转发：
```
location /api/ {
    proxy_pass http://172.17.0.2:8080/;  # 末尾添加斜杠
    # 其他代理配置保持不变
}
```
这样/api/xxx会被正确转发到http://172.17.0.2:8080/xxx，后端能匹配路由并触发CORS中间件。

统一CORS处理逻辑
移除Nginx中所有手动添加的CORS头配置，让Gin的CORS中间件完全处理，避免前后端配置冲突。若必须在Nginx处理，需添加always参数确保所有响应都带上头：

location /api/ {
    # 其他代理配置
    add_header Access-Control-Allow-Origin $http_origin always;
    add_header Access-Control-Allow-Methods "GET, POST, PUT, DELETE, OPTIONS, HEAD" always;
    add_header Access-Control-Allow-Headers "Origin, Content-Length, Content-Type, Authorization" always;
    add_header Access-Control-Allow-Credentials true always;
    add_header Access-Control-Max-Age 43200 always;

    # 直接处理OPTIONS预检请求
    if ($request_method = OPTIONS) {
        return 204;
    }
}

优化Docker代理地址
改用Docker容器名称作为代理地址（需确保Nginx和后端容器在同一Docker网络），避免IP变化导致的连接问题：
```
proxy_pass http://your-backend-container-name:8080/;
```

检查Gin中间件顺序
确保CORS中间件是第一个被注册的，在路由定义之前：

r := gin.Default()
// 先注册CORS中间件
r.Use(cors.New(cors.Config{...}))
// 再定义路由
r.GET("/api/xxx", handler)

验证方法

修改配置后重启Nginx和后端容器，用浏览器开发者工具查看响应头，确认Access-Control-Allow-Origin等字段存在；或用curl测试OPTIONS请求：

curl -X OPTIONS -H "Origin: https://mywebsite" -H "Access-Control-Request-Method: POST" https://mywebsite/api/test

检查响应头是否包含正确的CORS字段。

内容的提问来源于stack exchange，提问作者bread

使用Nginx代理后CORS Header丢失问题求助

问题背景 #

Gin后端CORS配置 #

浏览器错误提示 #

Nginx配置 #

已尝试的无效方案 #

解决方案 #

核心问题分析 #

修复步骤 #

验证方法 #