Hi Maxim, Just did that and work fine for me! The warning "chain contains anchor" is gone from qualys ssl test page, while OCSP stapling is on, as well as ssl_stapling_verify. Side note: after applying this patch, I realized my config was actually wrong: the ssl_certificate file was indeed lacking my ssl cert provider intermediate cert and the trust chain verification started to faby shumisha - Nginx Mailing List - English
Hi I'm facing this problem as well, though in a different context: OCSP stapling. Everything looks good without OCSP stapling: my ssl_certificate file contain my domain (wildcard) cert from AlphaSSL, that doesn't require any intermediate cert, so the domain cert is the only one in that file. However to enable OCSP stapling, I have to specify the full cert chain in ssl_trusted_certificate. I doby shumisha - Nginx Mailing List - English
Hi Francis, Thanks a lot for your message, I think I got things under control thanks to you! You're right, there's indeed a 301 thrown by nginx from http://subdomain.xxxx.net/admin to http://xxxx.net/admin/ (as shown by the curl output). I had tried server_name_in_redirect to off before, to no avail, but I tried again, just in case. I looked up the documentation again, and I realized:by shumisha - Nginx Mailing List - English
Hi All, I am running into a weird issue, after having configured nginx 0.7.67 (comes with debian 6) for serving PHP pages, with automatic subdomains. It works fine for the most part, but when requesting a url that correspond to an actual folder, but without a trailing slash, the subdomain recognition fails. Here is the start of the config: server { listen 80; # base domainby shumisha - Nginx Mailing List - English