I just found this ticket which appears to describe (and solve) the same issue http://trac.nginx.org/nginx/ticket/13by runesoerensen - Nginx Mailing List - English
It's possible to do what I want with the mod_ssl module for Apache. The relevant directive is called `SSLProxyVerify` http://httpd.apache.org/docs/2.2/mod/mod_ssl.html#SSLProxyVerify.by runesoerensen - Nginx Mailing List - English
I need to send data to some backend servers using HTTPS, but it seems like nginx doesn't verify the certificate on the backend server. For instance, if I specify `proxy_pass https://example.com` and the certificate on example.com is invalid, nginx still completes the request without any warning. I'd prefer it if nginx checked whether the certificate could be verified during the SSL handshake, aby runesoerensen - Nginx Mailing List - English
nginx -V returns: nginx version: nginx/1.2.0 TLS SNI support enabled configure arguments: --prefix=/etc/nginx --conf-path=/etc/nginx/nginx.conf --error-log-path=/var/log/nginx/error.log --http-client-body-temp-path=/var/lib/nginx/body --http-fastcgi-temp-path=/var/lib/nginx/fastcgi --http-log-path=/var/log/nginx/access.log --http-proxy-temp-path=/var/lib/nginx/proxy --http-scgi-temp-path=/varby runesoerensen - Nginx Mailing List - English
The problem occurs when reloading the configuration - where nginx usually exits the existing worker processes gracefully.by runesoerensen - Nginx Mailing List - English
Following an upgrade from nginx 1.0.2 to 1.0.11 I've experienced a problem with worker processes that are not shutting down. When looking in the list of running processes the worker processes appears to be shutting down but never actually exits. I've been using the ubuntu nginx ppa's for maverick. As the worker processes doesn't shut down nginx ends up consuming to much memory and is ultimatby runesoerensen - Nginx Mailing List - English
Hi Maxim, Thanks for looking into this - I may apply the fix you propose sometime in the future. The solution I ended up with was kind of weird. I simply put the ssl_certificate related directives inside a "faux" server directive, that's also the first server directive containing ssl directives. As nginx picks the first one it finds, the correct certificate is still being inheritedby runesoerensen - Nginx Mailing List - English
Ezra, Tried following the steps and configuration you provided, but I keep getting an empty reply from the server when I hit it. I can that the variable $answer is properly set to the expected value (something like http://some-ip), but for some reason it doesn't work. It hangs for as long as the keepalive_timeout is set to. Any pointers as to why this doesn't work would be highly appreciatedby runesoerensen - Nginx Mailing List - English
Hi, I've set up a ssl_certificate and ssl_certificate_key directives on the http level of my nginx configuration. The problem I'm facing is that starting/reloading nginx is getting slower and slower as more hosts (server directives) are added. The server has roughly 1000 SSL-enabled hosts that inherits the ssl certificate directives. I know nginx verifies the certificate when loading it, soby runesoerensen - Nginx Mailing List - English