Nginx cookie map regex remove + character

So this is my map map $http_cookie $session_id_value { default ''; "~^.*[0-9a-f]{32}\=(?[\w]{1,}+).*$" $session_value; } The cookie name = a MD5 sum the full / complete value of the cookie seems to cut of at a plus + symbol What would the correct regex to be to ignore / remove + symbols from

Re: HTTP To TCP Conversion

Thank you. Can you please share more info on this please. Posted at Nginx Forum: https://forum.nginx.org/read.php?2,273098,273181#msg-273181 ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx

Re: 100% CPU use in ngx_http_finalize_connection

Thanks Maxim, everything is looking great after the patch. On Fri, Mar 24, 2017 at 4:26 PM, Maxim Dounin wrote: > Hello! > > On Fri, Mar 24, 2017 at 02:11:12PM +0100, Richard Stanway wrote: > >> Hi Maxim, >> Thanks for the quick patch! I've applied it to our server and will

Re: 100% CPU use in ngx_http_finalize_connection

Hello! On Fri, Mar 24, 2017 at 02:11:12PM +0100, Richard Stanway wrote: > Hi Maxim, > Thanks for the quick patch! I've applied it to our server and will > monitor the results. Usually the problem starts to occur within 1-2 > hours of a restart, so I'll post again later today with an update. A

[nginx-ru-announce] nginx-1.11.12

Изменения в nginx 1.11.12 24.03.2017 *) Исправление: nginx мог нагружать процессор; ошибка появилась в 1.11.11. -- Maxim Dounin http://nginx.org/ ___ nginx-ru-announce mailing list

nginx-1.11.12

Изменения в nginx 1.11.12 24.03.2017 *) Исправление: nginx мог нагружать процессор; ошибка появилась в 1.11.11. -- Maxim Dounin http://nginx.org/ ___ nginx-ru mailing list nginx-ru@nginx.org

[nginx-announce] nginx-1.11.12

Changes with nginx 1.11.12 24 Mar 2017 *) Bugfix: nginx might hog CPU; the bug had appeared in 1.11.11. -- Maxim Dounin http://nginx.org/ ___ nginx-announce mailing list nginx-announce@nginx.org

nginx-1.11.12

Changes with nginx 1.11.12 24 Mar 2017 *) Bugfix: nginx might hog CPU; the bug had appeared in 1.11.11. -- Maxim Dounin http://nginx.org/ ___ nginx mailing list nginx@nginx.org

[nginx] release-1.11.12 tag

details: http://hg.nginx.org/nginx/rev/22be63bf21ed branches: changeset: 6944:22be63bf21ed user: Maxim Dounin date: Fri Mar 24 18:05:06 2017 +0300 description: release-1.11.12 tag diffstat: .hgtags | 1 + 1 files changed, 1 insertions(+), 0 deletions(-)

[nginx] nginx-1.11.12-RELEASE

details: http://hg.nginx.org/nginx/rev/7f394e433f00 branches: changeset: 6943:7f394e433f00 user: Maxim Dounin date: Fri Mar 24 18:05:05 2017 +0300 description: nginx-1.11.12-RELEASE diffstat: docs/xml/nginx/changes.xml | 16 1 files changed,

[nginx] Fixed CPU hog while freeing hc->busy after e662cbf1b932 (1.11.11).

details: http://hg.nginx.org/nginx/rev/1c43ac026c1d branches: changeset: 6942:1c43ac026c1d user: Maxim Dounin date: Fri Mar 24 16:26:12 2017 +0300 description: Fixed CPU hog while freeing hc->busy after e662cbf1b932 (1.11.11). Reported by Richard Stanway,

Re: proxy_set_header и наследие

Hi В случае конкретно заголовка Host - nginx испольузет первое из > полученных значений. Это поведение, впрочем, историческое, и > стоит подумать о том, чтобы возвращать в подобных случаях 400, т.к. > синтаксис заголовка Host нескольких значений не допускает, и > свежий RFC 7230 явно требует

Re: proxy_set_header и наследие

Hello! On Fri, Mar 24, 2017 at 03:32:41PM +0200, Vladimir Getmanshchuk wrote: > > > 2) Если делаешь proxy_set_header дважды (иногда пересекается из-за > > > include), то получаешь два хедера в HTTP запросе(от чего некоторые > > backends > > > сходят с ума, когда видят два хедера Host(например).

Re: proxy_set_header и наследие

Hi! 2017-03-23 19:00 GMT+02:00 Maxim Dounin : > Hello! > Спасибо за скорый и развернутый ответ. > Документация о таком поведение - явно говорит, > http://nginx.org/ru/docs/http/ngx_http_proxy_module.html#proxy_set_header: > > : Директивы наследуются с предыдущего уровня

Re: 100% CPU use in ngx_http_finalize_connection

Hi Maxim, Thanks for the quick patch! I've applied it to our server and will monitor the results. Usually the problem starts to occur within 1-2 hours of a restart, so I'll post again later today with an update. On Fri, Mar 24, 2017 at 2:03 PM, Maxim Dounin wrote: > Hello! >

Re: 100% CPU use in ngx_http_finalize_connection

Hello! On Fri, Mar 24, 2017 at 01:31:35PM +0100, Richard Stanway wrote: > Hello, > I recently moved our site to a new server running Linux 4.9, Debian > 8.7 64 bit with nginx 1.11.11 from the nginx repository. Our config is > straightforward - epoll, a few proxy backends and a few fastcgi >

Re: 100% CPU use in ngx_http_finalize_connection

I caught another loop, this time using nginx-debug with source. It seems it is stuck in a loop trying to ngx_pfree something that is already freed? I don't really understand the source enough to know what's going on, but the parameters to ngx_pfree are the same every time and the code keeps

100% CPU use in ngx_http_finalize_connection

Hello, I recently moved our site to a new server running Linux 4.9, Debian 8.7 64 bit with nginx 1.11.11 from the nginx repository. Our config is straightforward - epoll, a few proxy backends and a few fastcgi backends, a handful of vhosts, some with HTTP2, geoip module loaded. No AIO, no threads,

Re: Указатель на произвольные данные в структуре ngx_connection_s

Hello! On Fri, Mar 24, 2017 at 12:44:10PM +0300, Pavel Balaev wrote: > Добрый день. > > Я пытаюсь написать модуль, который должен хранить некоторые произвольные > данные на протяжении времени жизни сессии (keep-alive). В структуре > ngx_connection_s есть > пул памяти, при первом реквесте я

Re: nginx-1.11.11

Hello! On Thu, Mar 23, 2017 at 11:51:44PM +0400, Алексей Сундуков wrote: > > *) Добавление: улучшения в скриптах подсветки синтаксиса для vim. > А речь про этот файл: > https://trac.nginx.org/nginx/browser/nginx/contrib/vim/syntax/nginx.vim ? > Я правильно понимаю, что это эволюция вот этого >

custom data pointer in struct ngx_connection_s

Hello. I'm trying to write module for nginx. My module needs to hold some arbitrary data while connection is alive (keep-alive connection). The memory for void *ctx is allocated from r->commection->pool. The problem is that I don't know where to store this pointer. I added void *ctx to struct

nginx-ldap-auth помогите с настройкой пожалуйста

Добрый день. Подскажите пожалуйста как правильно настроить авторизацию через LDAP Делаю по инструкции : https://www.nginx.com/blog/nginx-plus-authenticate-users/ Подключаюсь к AD на Windows Server 2008 R2. При правильно логине и пароле получаю следующую ошибку: localhost - testnginx [24/Mar/2017

[PATCH 1 of 3] HTTP: add support for trailers in HTTP responses

# HG changeset patch # User Piotr Sikora # Date 1490351854 25200 # Fri Mar 24 03:37:34 2017 -0700 # Node ID a0f291f0a903b863161900f4d0cbb405f5d7a735 # Parent 39ff6939266e913e8bfd400e60f9520e70725a4d HTTP: add support for trailers in HTTP responses. Example:

[PATCH 2 of 3] Headers filter: add "add_trailer" directive

# HG changeset patch # User Piotr Sikora # Date 1490351854 25200 # Fri Mar 24 03:37:34 2017 -0700 # Node ID 6d878f4585b977053a9d00053bbb7aff263eb96c # Parent a0f291f0a903b863161900f4d0cbb405f5d7a735 Headers filter: add "add_trailer" directive. Trailers added using

Re: [PATCH 2 of 3] Upstream: allow recovery from "429 Too Many Requests" response

Hey Maxim, > Sure, but why one would use "proxy_next_upstream http_429" then? > > If one of your backends reject a requests based on client's IP / > login, then you probably don't want nginx to retry such a request > on other servers, as this will just allow the user to do more > requests when

[PATCH 2 of 2] Upstream: allow recovery from "429 Too Many Requests" response

# HG changeset patch # User Piotr Sikora # Date 1490348883 25200 # Fri Mar 24 02:48:03 2017 -0700 # Node ID b377cfedf632b14a3d459e12342a0557a25a790c # Parent 799ef976b58cadbc212bd790a666033d3777c10d Upstream: allow recovery from "429 Too Many Requests" response.

[PATCH 1 of 2] HTTP: add support for "429 Too Many Requests" response (RFC6585)

# HG changeset patch # User Piotr Sikora # Date 1490348883 25200 # Fri Mar 24 02:48:03 2017 -0700 # Node ID 799ef976b58cadbc212bd790a666033d3777c10d # Parent 39ff6939266e913e8bfd400e60f9520e70725a4d HTTP: add support for "429 Too Many Requests" response (RFC6585).

Указатель на произвольные данные в структуре ngx_connection_s

Добрый день. Я пытаюсь написать модуль, который должен хранить некоторые произвольные данные на протяжении времени жизни сессии (keep-alive). В структуре ngx_connection_s есть пул памяти, при первом реквесте я аллоцирую память для ctx = ngx_pcalloc(r->connection->pool,..., но проблема в том, что

access log to syslog

Добрый день. nginx1.11 Вот хочу access log писать на syslog сервер и оставлять локально. Делаю так access_log /var/log/nginx/access_conf.log main if=$confirm; access_log syslog:server=192.168.201.12,facility=local7,tag=nginx,severity=info; или так. access_log /var/log/nginx/access_conf.log main