在反向代理模式下使用NGINX压缩资产(Compressing assets with NGINX in reverse proxy mode)

 我在Node.js应用程序前面使用NGINX作为反向代理。 基本代理工作得非常好，我能够使用compression中间件compression节点服务器上的资产。 
 
 为了测试是否可以将压缩任务委托给NGINX，我已经禁用了中间件，现在我正在尝试使用以下配置使用NGINX进行gzip： 
 
worker_processes 1;

events {
    worker_connections 1024;
}

http {
    include mime.types;
    default_type application/octet-stream;
    sendfile on;
    keepalive_timeout 300;
    server {
        listen 80;

        ## gzip config
        gzip on;
        gzip_min_length 1000;
        gzip_comp_level 5;
        gzip_proxied any;
        gzip_vary on;
        gzip_types text/plain
                   text/css
                   text/javascript
                   image/gif
                   image/png
                   image/jpeg
                   image/svg+xml
                   image/x-icon;

        location / {
            proxy_pass http://app:3000/;
            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 Upgrade $http_upgrade;
            proxy_set_header Connection 'upgrade';
            proxy_cache_bypass $http_upgrade;
            }
    }
}
 
 使用此配置，NGINX不会压缩资产。 我尝试在location上下文中使用不同的选项声明这些，但它们似乎都没有。 
 
 我找不到相关的资源，所以我在质疑它是否可以这样做。 
 
 重点： 
 
 1-节点和NGINX在不同的容器上，所以我不使用NGINX服务静态资产。 我只是代理服务这些文件的节点服务器。 我想要实现的是卸载节点服务器，让NGINX进行gzipping。 
 
 2-我正在使用“Accept-Encoding：gzip”启用测试所有响应。 

I'm using NGINX as a reverse proxy in front of a Node.js app. The basic proxy works perfectly fine and I'm able to compress assets on the Node server with compression middleware.
 
To test if it's possible to delegate the compression task to NGINX, I've disabled the middleware and now I'm trying to gzip with NGINX with the following configuration:
 
worker_processes 1;

events {
    worker_connections 1024;
}

http {
    include mime.types;
    default_type application/octet-stream;
    sendfile on;
    keepalive_timeout 300;
    server {
        listen 80;

        ## gzip config
        gzip on;
        gzip_min_length 1000;
        gzip_comp_level 5;
        gzip_proxied any;
        gzip_vary on;
        gzip_types text/plain
                   text/css
                   text/javascript
                   image/gif
                   image/png
                   image/jpeg
                   image/svg+xml
                   image/x-icon;

        location / {
            proxy_pass http://app:3000/;
            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 Upgrade $http_upgrade;
            proxy_set_header Connection 'upgrade';
            proxy_cache_bypass $http_upgrade;
            }
    }
}
 
With this configuration, NGINX doesn't compress the assets. I've tried declaring these in the location context with different options but none of them seems to do the trick.
 
I couldn't find relevant resources on this so I'm questioning if it could be done this way at all.
 
Important points:
 
1- Node and NGINX are on different containers so I'm not serving the static assets with NGINX. I'm just proxying to the node server which is serving these files. All I'm trying to achieve is offload the node server with getting NGINX to do the gzipping.
 
2- I'm testing all the responses with "Accept-Encoding: gzip" enabled.

原文：https://stackoverflow.com/questions/46531021