Reverse Proxy - Issue in 0.8.36/.37
Kevin
nginx-forum at nginx.us
Sat Jun 5 04:04:32 MSD 2010
I can't really post my config with all information but I can post the specific configuration for the site's that have issues.
nginx 0.7.x does not show this problem.
If you configure a SSL reverse proxy:
server {
listen 192.168.12.2:1001;
ssl on;
ssl_certificate /usr/local/nginx/cert/apache-cert;
ssl_certificate_key /usr/local/nginx/cert/apache-key;
ssl_session_timeout 5m;
keepalive_timeout 15;
location / {
#limit_req zone=one burst=10;
proxy_read_timeout 300;
proxy_connect_timeout 300;
proxy_pass http://example.site.com:6043;
proxy_redirect off;
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 https;
}
}
Then it always gives 'Bad Gateway'. This issue was never present with 0.7.x
Setting proxy_pass to : https:// or http:// gives the same result.
Enabling or disabling buffering offers the same result.
Any ideas if this is a new bug? I have thus far, tested .36/.37 - I'm building .38 now to see if it's still an issue.
Any help would be greatly appreciated.
Posted at Nginx Forum: http://forum.nginx.org/read.php?2,94684,94684#msg-94684
More information about the nginx
mailing list