Hi, I started a NGINX Controller Trial andd used the Freemium non expiring Association token to activate my controller lisence. This worked fine .and my contorlelr shows as activated . I then followd this guide to download the cert and key for the nginx plus repo: https://docs.nginx.com/nginx-controller/admin-guides/install/get-n-plus-cert-and-key/ This also worked. I then followed the ngiby stephan13360 - Nginx Mailing List - English
Wow, thats it! The delay is gone. For now I am satisfied that the delay is gone and will read up some more on tcp_nopush. For the future: Is there any information on why the combination of tcp_nopush and proxy_cache_background_update create the delay and not the STALE response you get when the backend ist down and proxy_cache_background_update is off?by stephan13360 - Nginx Mailing List - English
To clarify a few things: The delay has nothing to do with the proxy_cache_valid 200 time, this change only made me realize that there seems to be a problem. Before this change our web monitoring would always get a cache HIT, and after it mostly got a STALE response because it checks every minute. We use NGINX 1.15.0 mainline.by stephan13360 - Nginx Mailing List - English
I recently set proxy_cache_valid 200 to 1 second, down from 15 minutes to refresh the content more often (With proxy_cache_background_update on; already activated long before that). Our Web monitoring, checking our site every minute, showed an increase in response time following this change. After some investigating I pinned it down to a ~200 ms delay coming from using proxy_cache_background_uby stephan13360 - Nginx Mailing List - English
Why should it redirect to https when you open http://www.domain.com/admin ? I don't see any "location /admin" block that would do that. If you want https only for /admin create a block like this: location /admin { return 301 https://www.domain.com/admin; } Better: If you have the ressources, why not redirect all traffic to https? server { listen 80; server_name wwby stephan13360 - How to...
This is just an understanding question, everything works, but i'm not quite sure why. My basic setup is a folder /var/www/test inside there is a "index.html" and another folder called "folder" and inside this folder another "index.html". === Config === server_name mydomain.com; root /var/www/test; location / { index index.html; try_files $uri $uri/by stephan13360 - How to...
SSL Stapling is working fine for me with just one line: ssl_stapling on; The SSL Labs Server Test shows that it is working. Then i found ssl_stapling_verify in the nginx docs. I know what it is supposed to do but i dont know if it is doing anything. Below is my configuration, as you can see i am using a startcom certificate. ssl_stapling on; ssl_trusted_certificate /etc/ssl/startcom.bunby stephan13360 - How to...
Thanks. I never even considered that the certificate could be the problem. Maxim Dounin Wrote: ------------------------------------------------------- > Hello! > > On Wed, Aug 21, 2013 at 01:19:01PM -0400, stephan13360 wrote: > > > Chrome 29 came out recently and now supports TLS 1.2. So i decided > to add > > some of the new TLS 1.2 ciphers to my webserver,by stephan13360 - Nginx Mailing List - English
Chrome 29 came out recently and now supports TLS 1.2. So i decided to add some of the new TLS 1.2 ciphers to my webserver, which are specified here: https://www.openssl.org/docs/apps/ciphers.html#TLS_v1_2_cipher_suites. My current setup is: Ubuntu 10.04, Nginx 1.5.3 ,OpenSSL 1.0.1e (build myself) Config file: server { listen 80; server_name sherbers.de; return 301 https:/by stephan13360 - Nginx Mailing List - English