AWS环境下Nginx代理Next.js接口出现502错误求助

问题背景 #

后端登录后会设置Cookie头存储refresh-token，前端（Next.js Pages Router）的服务端API调用时，会将该Cookie头返回给客户端，用于客户端独立调用API和SSR渲染。本地环境及本地搭建的Nginx均能正常运行，但在AWS环境中API返回502错误，Nginx日志出现两种报错：

• 设置Transfer-Encoding: ""时：upstream sent unknown "Transfer-Encoding": "" while reading response header from upstream
• 不清除Transfer-Encoding头时：upstream sent "Content-Length" and "Transfer-Encoding" headers at the same time while reading response header from upstream

服务端代码 #

try {
    const clientIp = requestIp.getClientIp(req);
    const { data, headers: returnedHeaders } = await postLogin(undefined, clientIp, 'api/auth/authenticate-anonymous');
    Object.entries(returnedHeaders).forEach(keyArr => {
        res.setHeader(keyArr[0], keyArr[1]);
    })
    res.setHeader('Transfer-Encoding', '');
    return res.send(data);
} catch (err) {
    return res.send(err);
}

Nginx配置（AWS Elastic Beanstalk） #

# Elastic Beanstalk Nginx Configuration File

user                    nginx;
error_log               /var/log/nginx/error.log warn;
pid                     /var/run/nginx.pid;
worker_processes        auto;
worker_rlimit_nofile    200000;

events {
    worker_connections  1024;
}

http {
    server_tokens off;

    include       /etc/nginx/mime.types;
    default_type  application/octet-stream;

    log_format  main  '$remote_addr - $remote_user [$time_local] "$request" '
                      '$status $body_bytes_sent "$http_referer" '
                      '"$http_user_agent" "$http_x_forwarded_for"';

    include       conf.d/*.conf;

    map $http_upgrade $connection_upgrade {
        default     "upgrade";
    }

    server {
        listen        80 default_server;
        access_log    /var/log/nginx/access.log main;

        client_header_timeout 60;
        client_body_timeout   60;

        keepalive_timeout     60;
        gzip                  on;
        gzip_comp_level       4;
        gzip_types text/plain text/css application/json application/javascript application/x-javascript text/xml application/xml application/xml+rss text/javascript;

        # Include the Elastic Beanstalk generated locations
        # include conf.d/elasticbeanstalk/*.conf;
        location / {
            proxy_pass          http://127.0.0.1:8080;
            proxy_http_version  1.1;

            # Proper proxy headers
            proxy_set_header    Host                $host;
            proxy_set_header    X-Real-IP           $remote_addr;
            proxy_set_header    X-Forwarded-For     $proxy_add_x_forwarded_for;
            proxy_set_header    X-Forwarded-Proto   $scheme;

            # Ensure buffering is enabled
            proxy_buffering     on;
            proxy_buffers       16 16k;
            proxy_buffer_size   16k;

            # Remove empty Transfer-Encoding headers from upstream
            proxy_hide_header   Transfer-Encoding;

            # proxy_set_header    Connection          $connection_upgrade;
            proxy_set_header Connection "";
            # proxy_set_header    Upgrade             $http_upgrade;
        }
    }
}

解决方案 #

1. 修复服务端代码：移除无效的Transfer-Encoding设置 #

HTTP规范中Transfer-Encoding头不能设为空值，当前代码中res.setHeader('Transfer-Encoding', '')是错误操作。正确做法是直接跳过或移除该头：

try {
    const clientIp = requestIp.getClientIp(req);
    const { data, headers: returnedHeaders } = await postLogin(undefined, clientIp, 'api/auth/authenticate-anonymous');
    
    // 遍历返回头时跳过Transfer-Encoding
    Object.entries(returnedHeaders).forEach(([key, value]) => {
        if (key.toLowerCase() !== 'transfer-encoding') {
            res.setHeader(key, value);
        }
    })
    
    return res.send(data);
} catch (err) {
    return res.send(err);
}

或者先设置所有头，再删除Transfer-Encoding：

// ...其他代码
Object.entries(returnedHeaders).forEach(keyArr => {
    res.setHeader(keyArr[0], keyArr[1]);
})
// 删除Transfer-Encoding头，而非设置为空
res.removeHeader('Transfer-Encoding');
return res.send(data);

2. 优化Nginx配置，处理头冲突 #

在location /块中替换原有的proxy_hide_header Transfer-Encoding;，改为直接忽略上游的Transfer-Encoding头，避免Content-Length和Transfer-Encoding共存：

# 忽略上游的Transfer-Encoding头，由Nginx自行处理响应长度
proxy_ignore_headers Transfer-Encoding;

3. 验证AWS配置生效 #

确保自定义Nginx配置文件放在Elastic Beanstalk的.ebextensions目录下（如.ebextensions/nginx.conf），部署后通过SSH登录实例，检查/etc/nginx/nginx.conf是否包含你的修改。

问题根源 #

本地Nginx对非法HTTP头的容忍度更高，而AWS环境中的Nginx严格遵循HTTP规范，空值的Transfer-Encoding头会被判定为无效请求，进而返回502错误。

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