nginx 1.9.12 proxy_cache always returns MISS

Been playing with this for 2 days. proxy_pass is working correctly but the proxy_cache_path remains empty whatever I make. Here's the source I use for tests: root@NC-PH-0657-10:/etc/nginx/snippets# curl -X GET -I http://www.kuriyama-truck.com/images/parts/13375/thumbnail_0/1_1.jpg HTTP/1.1 200

Re: nginx 1.9.12 proxy_cache always returns MISS

Yes it's resolved. I've change the cache path yesterday and a few minutes ago, I noticed that error message: "2016/03/19 12:31:02 [emerg] 8984#8984: cache "my_zone" uses the "/tmp/nginx/dev" cache path while previously it used the "/tmp/nginx" cache path" It seems it was enough to prevent the

Please help rewrite proper parameter

Hi, Sometimes, bots are notorious for doing that, arguments are over urlencoded. If someone knew a way to rewrite them back to their normal state, that would be awesome. e.g. Normal URL: www.site.com/file.php?param=blahblah URLs that bots try sometimes (often in fact - don't know where

Re: nginx 1.11.0: client sent stream with data before settings were acknowledged while processing HTTP/2 connection

Strange, cannot find 1.11.x Maybe you mean 1.10.0? root@NC-PH-0657-10:/usr/local/src/nginx# wget http://nginx.org/download/nginx-1.11.0.tar.gz --2016-04-29 10:53:26-- http://nginx.org/download/nginx-1.11.0.tar.gz Resolving nginx.org (nginx.org)... 206.251.255.63, 95.211.80.227,

Re: nginx is too greedy with urls

If you're from the apache world, nginx configuration if often counter-intuitive. Does the following help? # To find location matching a given request, nginx first checks locations defined # using the prefix strings (prefix locations). Among them, the location with the # longest matching prefix

Re: Please help rewrite proper parameter

For reference, that snippet seem to have done the job. I'm not redirecting them, I trash them though. if ($args ~* "^param\%"){ access_log off; return 410; } Posted at Nginx Forum: https://forum.nginx.org/read.php?2,265514,266528#msg-266528 ___

emergency msg after changing cache path

Got this message after changing the cache path? Could not find a solution after googling it. Any help? [emerg] 15154#15154: cache "my_zone" uses the "/dev/shm/nginx" cache path while previously it used the "/tmp/nginx" cache path nginx -V nginx version: nginx/1.11.3 built with OpenSSL 1.0.2h

Re: emergency msg after changing cache path

Interesting! Thank you so much! Posted at Nginx Forum: https://forum.nginx.org/read.php?2,269405,269415#msg-269415 ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx

Re: nginx-1.11.6

Hi, I build it every time a new version is available. This one didn't make it. System is Debian 8 jessie (...) /usr/local/src/nginx/nginx-1.11.6/debian/modules/nginx-upstream-fair/ngx_http_upstream_fair_module.c: In function ‘ngx_http_upstream_init_fair_rr’:

Re: nginx-1.11.6

Thanks for the details. I've recompiled without the nginx-upstream-fair module and all went well. It looks unmaintened and I don't really need it. Code is 8 years old. Best! Posted at Nginx Forum: https://forum.nginx.org/read.php?2,270963,270974#msg-270974

Re: limit_req per subnet?

I rate limit them using the user-agent Posted at Nginx Forum: https://forum.nginx.org/read.php?2,271483,271524#msg-271524 ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx

Re: limit_req per subnet?

I've inplemented something based on https://community.centminmod.com/threads/blocking-bad-or-aggressive-bots.6433/ Works perfectly fine for me. Posted at Nginx Forum: https://forum.nginx.org/read.php?2,271483,271535#msg-271535 ___ nginx mailing list

Re: server listen directive for IPV4 and IPV6

Excellent. Very grateful for the clarification! Maxim Dounin Wrote: --- > > If you want nginx to listen on both IPv4 and IPv6, you have to use > both > > listen 80; > > and > > listen [::]:80; > > in your configuration. > >

server listen directive for IPV4 and IPV6

There is a lot of confusion in the answers I fount about it. When I installed nginx first, it was the debian jessie version 1.6.2 and the configuration to listen to both ipv4 and ipv6 was #server { # listen 80; # listen [::]:80; # # server_name example.com; # # root

Re: Welcome to nginx on Debian!

/var/www/html/index.nginx-debian.html Posted at Nginx Forum: https://forum.nginx.org/read.php?2,273701,273710#msg-273710 ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx

Re: conflicting rules

yes of course I've reordered them too: location = /Scripts/awstats_misc_tracker.js { access_log on; } location ~* ^.+\.(css|js)$|^/(css|Scripts|uploads)/ { expires 50d; access_log off; log_not_found off; add_header Cache-Control "public"; } nginx -t nginx: the

conflicting rules

Hello, I exclude the stylesheets and javascript from the logs to alleviate them. However I would want to make an exception for awstats. So far the following doesn't work. Any help? location ~* ^.+\.(css|js)$|^/(css|Scripts|uploads)/ { expires -1; access_log off; log_not_found

Re: conflicting rules

Thanks, unfortunately it does not work grep awstat nginx/access.log |wc -l 0 Posted at Nginx Forum: https://forum.nginx.org/read.php?2,276715,276718#msg-276718 ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx

Re: conflicting rules

1 - If I disable that section #location ~* ^.+\.(css|js)$|^/(css|Scripts|uploads)/ { #expires -1; #access_log off; #log_not_found off; #} location = /Scripts/awstats_misc_tracker.js { access_log on; } the javascript are shown in the log. /Scripts/awstats_misc_tracker.js isn't though. 2

Re: conflicting rules

I'm positive. Posted at Nginx Forum: https://forum.nginx.org/read.php?2,276715,276723#msg-276723 ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx

Re: conflicting rules

Hey, nice catch, thanks so much! access_log on is not defeating access_log off; replaced the directive with: location = /Scripts/awstats_misc_tracker.js { } Thanks to both of you. Solved. Posted at Nginx Forum: https://forum.nginx.org/read.php?2,276715,276725#msg-276725

Re: Enabling both gzip & brotli

Yes, but I prefer to generate the *.br first and use brotli_static on; instead The browser will happily download the *.br if supported; otherwise gzip will be selected. Posted at Nginx Forum: https://forum.nginx.org/read.php?2,277282,277284#msg-277284

Re: rewrite question

'if ($args ~ "$") { return 400; }' Thanks a lot! Exactly what I needed :) Posted at Nginx Forum: https://forum.nginx.org/read.php?2,94128,280124#msg-280124 ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx

rewrite question

Hi, Recently, Google has started spidering my website and in addition to normal pages, appended "" to all urls, even the pages excluded by robots.txt e.g. page.php?page=aaa -> page.php?page=aaa Any idea how to redirect/rewrite this? Posted at Nginx Forum:

Re: TLS 1.3 not being selected.

Ah! Thank you very much. Recompiled with older openssl 1.1.1 pre2 since current browsers implement draft 23 atm. It's working now. Posted at Nginx Forum: https://forum.nginx.org/read.php?2,280017,280094#msg-280094 ___ nginx mailing list

Re: rewrite question

I see another poster have written this, and deleted it afterwards. `This is almost certainly not Google as they obey robots.txt. The & to conversion is another sign of a poor quality crawler. Check the RDNS and you will find it's probably some IP faking Google UA, I suggest blocking at network

Re: rewrite question

'The & to conversion is another sign of a poor quality crawler.' I wasn't referring to any of them but to ''. Important difference. Also explaining my failure to filter it from parameters since parameters contains an equal sign. E.g. ...= something or even = & or would also easy do filter

TLS 1.3 not being selected.

Hi, I can't see what I'm doing wrong. When I visit https://www.cloudflare.com/ with my browser TLS 1.3 is used. However when I visit my website, TLS 1.2 is selected instead. My browser (opera 53) has this in its command line: " --ssl-version-max=tls1.3 --tls13-variant=draft" Nginx is compiled

variable for domain name in redirect

Hello, I have something in one of my server bloc: ``` # switch to TLS for page.php, contact.php, faq.php, known https sources and / if ($scheme = http) { set $rule_9 1$rule_9; } if ($outdated = 0){ set $rule_9 2$rule_9; } if ($request_uri ~

OPTIONS request failing when issued from CDN

I could make it easily from localhost: curl -i -X OPTIONS http://www.server.com/css/reset.css -> xxx.xxx.xxx.190 - - [30/Jun/2018:11:33:53 -0700] "OPTIONS /css/reset.css HTTP/1.1" 200 0 "-" "curl/7.38.0" HTTP/1.1 200 OK Server: nginx Date: Sat, 30 Jun 2018 18:47:49 GMT Content-Type: text/css

Re: variable for domain name in redirect

> In most cases, $server_name is the variable you want. Thanks so much. Works like a charm. This simplifies my configuration/maintenance a lot. Best! Posted at Nginx Forum: https://forum.nginx.org/read.php?2,280353,280360#msg-280360 ___ nginx

499 and set $loggable 0;

Any idea on how to keep those 499 errors out of the logs? I already do it for some specific 444 if specific condition { set $loggable 0; return 444; } Posted at Nginx Forum: https://forum.nginx.org/read.php?2,278092,278092#msg-278092 ___ nginx

Re: SSL errors, verbosity level

> You may want to update OpenSSL. Thanks but I did and almost zero browser was able to use draft 26 or 28. Therefore I downgraded OpenSSL from 1.1.1-pre8 to 1.1.1-pre2 (draft 23). Although TLS 1.3 has been finalized, Openssl 1.1.1 is still work in progress. Tested with latest Opera, Palemoon,

Re: SSL errors, verbosity level

> Those unsupported ssl version messages should be in "info" level That is a very useful patch, many thanks Frank Posted at Nginx Forum: https://forum.nginx.org/read.php?2,280446,280496#msg-280496 ___ nginx mailing list nginx@nginx.org

Re: SSL errors, verbosity level

> Since you are using newer openssl, you may want to apply this patch I agree, many thanks to Piotr Sikora and to you, Frank! 2nd patch applied as well. My error log is a lot more readable now. I can see those real critical messages without being cluttered by meaningless/unfixable SSL issues.

SSL errors, verbosity level

Hi, I see those messages in my error logs daily. ``` 2018/07/07 08:01:32 [crit] 31935#31935: *342781 SSL_do_handshake() failed (SSL: error:14209102:SSL routines:tls_early_post_process_client_hello:unsupported protocol) while SSL handshaking, client: 173.208.91.177, server: 0.0.0.0:443 2018/07/07

Re: 1.13.9 compile errors

Maxim Dounin Wrote: --- > > The following patch should fix this, please test if it works for > you: > > # HG changeset patch > # User Maxim Dounin > # Date 1520919437 -10800 > # Tue Mar 13 08:37:17 2018 +0300 > # Node