Custom Query (2297 matches)

After updating from nginx 1.3.8 to 1.3.10, the reverse proxy functionality of nginx is no longer working properly.

My configuration:

        location / { 
                proxy_set_header X-Forwarded-Host $host;
                proxy_set_header X-Forwarded-Server $host;
                proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
                proxy_set_header X-Real-IP $remote_addr;

                proxy_set_header Host links.x-way.org;
                proxy_pass https://77.37.18.97/;
        }

Sample log entries:

==> /var/log/nginx/links.x-way.org.error.log <==
2013/01/07 17:17:47 [error] 18026#0: *384 connect() failed (110: Connection timed out) while connecting to upstream, client: 216.151.139.39, server: links.x-way.org, request: "GET /register.php/ HTTP/1.0", upstream: "https://77.37.18.97:0/r
egister.php/", host: "links.x-way.org", referrer: "https://www.links.x-way.org/about.php/"

==> /var/log/nginx/links.x-way.org.access.log <==
216.151.139.39 - - [07/Jan/2013:17:17:47 +0100]  "GET /register.php/ HTTP/1.0" 502 568 "https://www.links.x-way.org/about.php/" "Mozilla/5.0 (Windows NT 6.0) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.112 Safari/535.1" 21.827

From the log file we see that it is using port '0' to access the 77.37.18.97 backend instead of port '443' (for https).

When explicitely specifing '443' as port in the proxy_pass directive like below, the connection to the backend works fine.

        location / {
                proxy_set_header X-Forwarded-Host $host;
                proxy_set_header X-Forwarded-Server $host;
                proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
                proxy_set_header X-Real-IP $remote_addr;

                proxy_set_header Host links.x-way.org;
                proxy_pass https://77.37.18.97:443/;
        }

So I guess, the problem is that the default port for the proxy_pass directive is no longer properly set (eg. 80 when proxy_pass starts with ​http:// and 443 when it starts with ​https://).

When I call $r->header_in('cookie'), it is always returned as undef.

This works properly in previous versions, such as 1.3.1.

Other calls headers, such as 'User-Agent' still work just fine.

Hi compiled Nginx 1.13.9 from master branch to try out HTTP/2 Server Push but noticed the pushed assets loose their gzip compression and are served as non-compressed assets instead of compressed assets. Confirmed with Chrome devtool network inspection, nghttp tool and webpagetest.org that pushed assets are uncompressed. Seems similar to mod_h2 bug at ​https://github.com/icing/mod_h2/issues/86

Details at:

​https://community.centminmod.com/threads/hurray-http-2-server-push-for-nginx.11910/#post-59411

​https://forum.nginx.org/read.php?2,278481

System:

CentOS 7.4 64bit