nginx 配置http2代理

nginx 配置http2代理

经验文章nimo972025-06-21 22:35:082A+A-

1, /etc/nginx/conf/proxy.conf

# HTTPS 服务器 (支持 HTTP/2)
server {
    listen 443 ssl http2;
    server_name localhost;
    
    # SSL 证书配置
    ssl_certificate     /work/go/test/http2_sse/server/cert.pem;
    ssl_certificate_key /work/go/test/http2_sse/server/key.pem;
    
    # SSL 协议和加密套件配置
    ssl_protocols TLSv1.2 TLSv1.3;
    ssl_prefer_server_ciphers on;
    ssl_ciphers ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384;
    
    # SSL 会话缓存和超时
    ssl_session_cache shared:SSL:10m;
    ssl_session_timeout 1d;
    ssl_session_tickets off;
    
    # OCSP Stapling
    ssl_stapling off;
    ssl_stapling_verify off;

    #ssl_stapling on;
    #ssl_stapling_verify on;
    resolver 8.8.8.8 8.8.4.4 valid=300s;
    resolver_timeout 5s;
    
    # HSTS 配置
    add_header Strict-Transport-Security "max-age=31536000" always;
    
    # 代理设置
    location / {
        # 基本代理设置
        #proxy_pass https://localhost:8443;
        proxy_pass https://127.0.0.1:8443;
        proxy_http_version 1.1;
        
        # 代理头信息
        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;
        proxy_set_header X-Forwarded-Host $host;
        proxy_set_header X-Forwarded-Port $server_port;
        
        # 连接和超时设置
        proxy_buffering on;
        proxy_buffer_size 16k;
        proxy_buffers 4 32k;
        proxy_busy_buffers_size 64k;
        proxy_connect_timeout 60s;
        proxy_send_timeout 60s;
        proxy_read_timeout 60s;
        
        # 保持连接
        proxy_set_header Connection "";
        
        # WebSocket 支持
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade";
    }
    
    # 静态文件缓存 (可选)
    location ~* \.(jpg|jpeg|png|gif|ico|css|js)$ {
        expires 30d;
    }
}


注意: listen 443 ssl http2;

如果是自签名的证书:

ssl_stapling off;

ssl_stapling_verify off;

proxy_http_version 1.1; 这里为什么是1.1呢?

为什么大多数场景使用 HTTP/1.1?

  1. 兼容性:HTTP/1.1 是最广泛支持的协议,几乎所有后端服务器(如 Node.js、Tomcat、Apache)都支持。
  2. 性能足够:HTTP/1.1 的长连接(Keep-Alive)和分块传输已能满足多数场景需求。
  3. 简化配置:无需处理 HTTPS 证书验证、TLS 握手等复杂性。

总结

  • 不要设置 proxy_http_version 2:该指令不支持 HTTP/2。
  • 如果后端支持 HTTP/2:使用 grpc_pass 或 upstream 中的 http2 参数。
  • 默认使用 HTTP/1.1:这是最安全、兼容性最好的选择。

对比总结

场景

前端协议

后端协议

配置方式

前端 HTTP/2 → 后端 HTTP/1.1

HTTP/2

HTTP/1.1

proxy_pass http://backend;
proxy_http_version 1.1;

前端 HTTP/2 → 后端 HTTP/2

HTTP/2

HTTP/2

grpc_pass grpc://backend; 或
upstream backend { server backend:443 http2; }
proxy_pass https://backend;

点击这里复制本文地址 以上内容由nimo97整理呈现,请务必在转载分享时注明本文地址!如对内容有疑问,请联系我们,谢谢!
qrcode

尼墨宝库 © All Rights Reserved.  蜀ICP备2024111239号-7