Re: DNS Caching Issue For community version

Maybe You should try this module: https://github.com/GUI/nginx-upstream-dynamic-servers Regards, Biazus On Fri, May 13, 2016 at 3:13 AM, RT.Nat wrote: > Not clear regarding, " Also you might check using directly the hostname as > it might be possible that there is a bug when usin

Re: cache file has too long header (bug) ?

imes the object the caused the message appeared only once on the access log, so I don't think it was caused by a concurrency. Best Regards, Biazus Posted at Nginx Forum: http://forum.nginx.org/read.php?2,261567,261569#msg-261569 ___ nginx maili

cache file has too long header (bug) ?

Hey Guys, I've been using nginx 1.8.0 for a couple of months, and I noticed a critical message at error log informing that "cache file has too long header". 2015/09/10 17:11:03 [crit] 27245#0: *10686 cache file "/data/smallfiles/http/6/d8/f5df8d6eda60819319688d1bc0cb2d86" has too long header Ho

Re: How to cache js/css request containing a question mark?

Please try to remove $ in the end of the expression: something like this: location ~ .*\.(js|css) { expires 7d; } Also, make sure you are using args in the cache key: proxy_cache_key "$host$uri$is_args$args"; Regards, Biazus Posted at Nginx Forum: http://forum.nginx.or

Re: Persistent connections timeout (keepalive on upstream)

Yes, they do recicle, but it will depends how the keep alive timeout is configured in the backend. I believe there is a similar topic here: http://forum.nginx.org/read.php?2,249924,249953 Regards, Biazus Posted at Nginx Forum: http://forum.nginx.org/read.php?2,261284,261290#msg-261290

Re: Persistent connections timeout (keepalive on upstream)

Hi, You may check dynamic upstream module: https://github.com/GUI/nginx-upstream-dyanmic-servers Alternatives: http://www.senginx.org/en/index.php/Dynamic_DNS_Resolve http://openresty.org/ Regards, Biazus Posted at Nginx Forum: http://forum.nginx.org/read.php?2,261284,261285#msg-261285

Re: disable 301 redirect for directory / use relative redirect / change scheme

Please try something like that: proxy_redirect http://$proxy_host/ $scheme://$host/; Regards, Biazus Posted at Nginx Forum: http://forum.nginx.org/read.php?2,261275,261283#msg-261283 ___ nginx mailing list nginx@nginx.org http

Re: Cache structs 1.6.x vs 1.8.x

Hi Guys, We have developed a "cache migration tool" in order to keep the cache compatibility between Nginx 1.6.x and 1.8.x. Comments and suggestions are welcome! https://github.com/acaciocenteno/ngx_scripts Thanks, Biazus Posted at Nginx Forum: http://forum.nginx.or

Re: Ocsp stapling

Config files seems to be OK. Just make sure "ssl_trusted_certificate" contais the intermediate & root certificates (in that order from top to bottom). You can test with the following command: echo QUIT | openssl s_client -connect yourhost.com:443 -status 2> /dev/null | grep -A 17 'OCSP response:'

Re: Ocsp stapling

I have been using Nginx 1.8.X with ocsp stabling for a couple of weeks and it seems to be fine. Please send your config files, it may help... Posted at Nginx Forum: http://forum.nginx.org/read.php?2,261177,261181#msg-261181 ___ nginx mailing list nginx

Cache structs 1.6.x vs 1.8.x

-Encoding,User-Agent Thank in advance. Biazus Posted at Nginx Forum: http://forum.nginx.org/read.php?2,261151,261151#msg-261151 ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx

Re: Accept Header / cache versioning issue

I got it! The "issue" was the origin server sending "Vary: Accept" header. In order to avoid this behaviour, simply set "proxy_ignore_headers Vary;" Thanks! Posted at Nginx Forum: http://forum.nginx.org/read.php?2,261128,261131#msg-261131 ___ nginx m

Accept Header / cache versioning issue

alize the Accept header, or even ignore it ? Thanks in advance, Biazus Posted at Nginx Forum: http://forum.nginx.org/read.php?2,261128,261128#msg-261128 ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx

wrong data in $upstream_status and $upstream_response_time

“8.005, 0.242" As you can see, the data contain two or three values separated by a comma, and also the $upstream_response_time contain two time values, both separated by comma. Is that make sense to you guys ? Is it expected ? Thanks in advance, Daniel Biazus Posted at Nginx Forum: