Re: Очень медленный ответ после нескольких быстрых ответов

Поскольку с помощью опций nginx нельзя, я сделал отмену предыдущего запроса в приложении (как многократно рекомендовалось). Работает быстро и без ошибок. Спасибо всем за рекомендации и прояснения! Posted at Nginx Forum: https://forum.nginx.org/read.php?21,276486,276726#msg-276726

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: conflicting rules

On Thu, Oct 05, 2017 at 02:40:03PM -0400, shiz wrote: Hi there, > Thanks, unfortunately it does not work > > grep awstat nginx/access.log |wc -l > 0 http://nginx.org/r/access_log Look in the log file called "on", not in the log file called "nginx/access.log". f -- Francis Daly

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

And you're sure about the CaSe, right?  I notice that everything is lowercase for you except for the Scripts directory. On 10/5/2017 12:15 PM, shiz wrote: 1 - If I disable that section #location ~* ^.+\.(css|js)$|^/(css|Scripts|uploads)/ { #expires -1; #access_log off; #log_not_found off;

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

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

Re: conflicting rules

On 10/5/2017 11:40 AM, shiz wrote: Thanks, unfortunately it does not work Did you reload the config after you modified it? Igal Sapir Lucee Core Developer Lucee.org ___ nginx mailing list nginx@nginx.org

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: ngx_http_mirror_module в стабильной версии

On Thursday 05 October 2017 20:41:17 Andrey Kopeyko wrote: > Добрый день, товарищи! > > Вопрос к сотрудникам компании NGINX, Inc - в какие, примерно, сроки > можно ожидать появления модуля ngx_http_mirror_module в стабильной > версии nginx? Случится ли это до НГ? > > Спрашиваю потому, что

Re: conflicting rules

Hi, On 10/5/2017 11:25 AM, shiz wrote: 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 ~* ^/Scripts/awstats_misc_tracker.js { access_log on; }

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: ngx_http_mirror_module в стабильной версии

Hello! On Thu, Oct 05, 2017 at 08:41:17PM +0300, Andrey Kopeyko wrote: > Добрый день, товарищи! > > Вопрос к сотрудникам компании NGINX, Inc - в какие, примерно, сроки > можно ожидать появления модуля ngx_http_mirror_module в стабильной > версии nginx? Случится ли это до НГ? Очередная

ngx_http_mirror_module в стабильной версии

Добрый день, товарищи! Вопрос к сотрудникам компании NGINX, Inc - в какие, примерно, сроки можно ожидать появления модуля ngx_http_mirror_module в стабильной версии nginx? Случится ли это до НГ? Спрашиваю потому, что функционал этот зело полезен в запускающемся проекте, но одновременно есть

Re: [PATCH] Proxy: tcp fast open in client mode

Hello! On Thu, Oct 05, 2017 at 03:12:42PM +0200, Jan Prachař wrote: > What do you think about adding support for tcp fast open in the proxy > module when connecting to upstream? I'm somewhat sceptical. It seems to be limited to very few use cases, and also there are lot of corner cases to

[nginx] Upstream hash: reordered peer checks.

details: http://hg.nginx.org/nginx/rev/3b4fa572d56d branches: changeset: 7124:3b4fa572d56d user: Maxim Dounin date: Thu Oct 05 17:43:05 2017 +0300 description: Upstream hash: reordered peer checks. This slightly reduces cost of selecting a peer if all or almost

[njs] Improved editline detection on NetBSD.

details: http://hg.nginx.org/njs/rev/d6ab83febe2b branches: changeset: 416:d6ab83febe2b user: Dmitry Volyntsev date: Thu Oct 05 18:23:22 2017 +0300 description: Improved editline detection on NetBSD. diffstat: nxt/auto/editline | 10 ++ 1 files changed,

[nginx] Fixed build without IPv6, broken by 874171c3c71a.

details: http://hg.nginx.org/nginx/rev/935b1902a7dd branches: changeset: 7122:935b1902a7dd user: Maxim Dounin date: Thu Oct 05 16:50:35 2017 +0300 description: Fixed build without IPv6, broken by 874171c3c71a. diffstat: src/core/ngx_inet.c | 4 +++- 1 files

Re: nginx null bytes on static image

Hello! On Thu, Oct 05, 2017 at 08:57:14AM -0400, soulseekah wrote: > Thanks. Turning off sendfile worked, but a small test program in C on the > same filesystem doesn't yield this behavior. > What else could I test to reproduce this and confirm OS or filesystem > issues? If you are able to

[PATCH] Proxy: tcp fast open in client mode

What do you think about adding support for tcp fast open in the proxy module when connecting to upstream? --- nginx/conf/nginx/nginx.conf| 1 + nginx/contrib/vim/syntax/nginx.vim | 1 + nginx/src/core/ngx_connection.h| 1 +

Re: nginx null bytes on static image

Thanks. Turning off sendfile worked, but a small test program in C on the same filesystem doesn't yield this behavior. What else could I test to reproduce this and confirm OS or filesystem issues? Thanks for your time and ideas. Posted at Nginx Forum:

[njs] Fixed default makefile target is libedit is unavailable.

details: http://hg.nginx.org/njs/rev/d0e24fa20991 branches: changeset: 412:d0e24fa20991 user: Dmitry Volyntsev date: Thu Oct 05 15:50:16 2017 +0300 description: Fixed default makefile target is libedit is unavailable. Previously, if libedit was unavailable, any

[njs] Fixed various dead store assignments.

details: http://hg.nginx.org/njs/rev/b4462c7dc1b1 branches: changeset: 414:b4462c7dc1b1 user: Dmitry Volyntsev date: Thu Oct 05 15:50:36 2017 +0300 description: Fixed various dead store assignments. diffstat: njs/njs_json.c | 2 +-

[njs] Skipping expect tests if libedit is not available.

details: http://hg.nginx.org/njs/rev/6789d9142b05 branches: changeset: 413:6789d9142b05 user: Dmitry Volyntsev date: Thu Oct 05 15:50:17 2017 +0300 description: Skipping expect tests if libedit is not available. diffstat: nxt/auto/editline | 2 ++

Using request URI path to store cached files instead of MD5 hash-based path

Hi, If proxy caching is enabled, NGINX is saving the files under subdirectories of the proxy_cache_path, based on the MD5 hash of the cache-key and the levels parameter value. Is it possible to change this behaviour through configuration to cache the files using the request URI path itself, say,