In Nginx revers proxy unable to disable TLS1

Hi Team, I have deployed nginx in reverse proxy mode and trying to disable TLS1 and1.1 in configuation file but somehow it still shows when site is scanned by SSLlabs. Any idea why? nginx version: nginx/1.10.1 ssl_prefer_server_ciphers On; ssl_protocols TLSv1.2; ssl_cip

Recommended method to debug POST requests?

While searching for a way to debug POST requests in NGINX 1.15, I found a link to https://github.com/openresty/echo-nginx-module (the "HTTP Echo" module) on https://www.nginx.com/resources/wiki/modules/ . Is HTTP Echo the recommended way to go, or are there any alternatives, ideally methods that d

Nginx tries to open the html file and through error 404. I expected the redirection to the php script

Hi, Nginx tries to open the html file and through error 404. I expected the redirection to the php script. server { listen 443 ssl http2 fastopen=500 reuseport; listen [::]:443 ssl http2 fastopen=500 reuseport ipv6only=on; server_name www.testing.com.uy; resolver 1.1.1.1 1.0.0.1

Fail_timeout behaviour on no available servers

hi, In nginx 1.11.5, this change was introduced - Change: now if there are no available servers in an upstream, nginx will not reset number of failures of all servers as it previously did, but will wait for fail_timeout to expire Is there any way via configuration to change this be

Re: Problems with cache by mime/type

ahh! > At the time that nginx is deciding "should this request be served from > cache or sent to upstream?", $upstream_http_content_type cannot have > a value. > now I figured out the reason. thank you Francis. ___ nginx mailing list nginx@nginx.org htt

Re: Problems with cache by mime/type

On Fri, Nov 30, 2018 at 11:32:39AM -0200, Jorge Pereira wrote: Hi there, > I sent the wrong snip. the correct is using > $upstream_http_content_type as can be seen below. basically, always $upstream_http_content_type is the http Content-Type header sent by upstream in response to the request fro

Re: Problems with cache by mime/type

Hi Francis, I sent the wrong snip. the correct is using $upstream_http_content_type as can be seen below. basically, always when I use "proxy_cache_bypass $no_cache;" that impact the value of "map $upstream_http_content_type $no_cache" I didn't understand what is the reason. thanks for any su

Re: Problems with cache by mime/type

On Thu, Nov 29, 2018 at 09:51:13PM -0200, Jorge Pereira wrote: Hi there, > I am using the nginx/1.12.0 and I am trying to use the below config. > but, the below "map" by "$upstream_http_content_type" is always > matching with default value "1". but, if I remove "proxy_cache_bypass" > then the map

Re: Inner workings of nginx cache manager

Hi! So the cache loader only does something like stat() during the filesystem walk, which should be fairly fast, unless you have tens/hundreds of millions of files in cache. Thanks again! Stefan On Fri, Nov 30, 2018 at 1:58 PM Maxim Dounin wrote: > Hello! > > On Fri, Nov 30, 2018 at 01:26:27P

Re: Inner workings of nginx cache manager

Hello! On Fri, Nov 30, 2018 at 01:26:27PM +0100, Stefan Safar wrote: > So the process/thread that scans through the files on disk need to read the > all the file headers to find the KEY for the all cache files to keep the > information in memory before it starts deleting anything, is that correct

Re: Inner workings of nginx cache manager

Hi Maxim, thanks a lot for the clarification! So the process/thread that scans through the files on disk need to read the all the file headers to find the KEY for the all cache files to keep the information in memory before it starts deleting anything, is that correct? It would be great if I cou