Re: nginx-1.27.0 - shasum does not match with expected shasum from pkg-oss

On 29/05/2024 17:22, Igor Ippolitov wrote: On 29/05/2024 16:52, Daniel Jagszent wrote: Hello, the SHA512 of https://nginx.org/download/nginx-1.27.0.tar.gz (downloaded 2024-05-29 15:42:02 UTC) is

Re: nginx-1.27.0 - shasum does not match with expected shasum from pkg-oss

On 29/05/2024 16:52, Daniel Jagszent wrote: Hello, the SHA512 of https://nginx.org/download/nginx-1.27.0.tar.gz (downloaded 2024-05-29 15:42:02 UTC) is 251bfe65c717a8027ef05caae2ab2ea73b9b544577f539a1d419fe6adf0bcc846b73b58f54ea3f102df79aaf340e4fa56793ddadea3cd61bcbbe2364ef94bacb This does not

Re: Nginx prematurely closing connections when reloaded

ien Le jeu. 28 mars 2024, 16:40, Igor Ippolitov a écrit : Sébastien, The message about the signal process is only the beginning of the process. You are interested in messages like the following: 2024/03/26 13:36:36 [notice] 723#723: signal 1 (SIGHUP) received from 6906

Re: Nginx prematurely closing connections when reloaded

5#0: signal process started --- END --- I did not configure worker_shutdown_timeout, it is unlimited. Sébastien. Le lun. 25 mars 2024 à 17:59, Igor Ippolitov a écrit : Sébastien, Nginx should keep active connections open and wait for a request to complete before closing. A re

Re: Nginx prematurely closing connections when reloaded

Sébastien, Nginx should keep active connections open and wait for a request to complete before closing. A reload starts a new set of workers while old workers wait for old connections to shut down. The only exception I'm aware of is having worker_shutdown_timeout configured: in this case a wor

Re: number of keepalive connections to an upstream

Sébastien, Keepalive in an upstream defines a pool of connections attached to that upstream. The main purpose of the pool is to reduce the amount of new TCP connections: the fewer new connections you open the less load you have. Any specific recommendation will fail in some case. So the real

Re: Njs 0.7.7

Evert, Which repository are you using? Try setting up a repo using this doc: http://nginx.org/en/linux_packages.html Let me know if you face issues with it. Regards, Igor On 15/09/2022 15:44, Evert Saar wrote: Njs 0.7.7 looks great. How to use it? Latest public nginx 1.23.1 supports 0.7.6

Re: Client can't negotiate with TLS 1.0 and 1.1

Fabiano, Is it possible that you have nginx.org/r/ssl_reject_handshake configured in another server block listening on 10.0.0.2:443? Is there anything useful in nginx error log? My guess, using -servername option will resolve the issue for you. Regards, Igor. On 24/08/2022 21:22, Fabiano Fur

Re: listen on IPs but do not fail if one is absent - ?

Hello, I would give a try to 'net.ipv4.ip_nonlocal_bind' sysctl knob. Set it to true and bind() won't fail. Regards, Igor. On 12/02/2022 10:11, lejeczek via nginx wrote: Hi guys a novice here so go easy on me with this question: having multiple 'listen' with IPs or, just one 'listen' with

Re: map problem : how to debug it ?

Gilles, When you enter a url with an anchor into a browser, the browser will only request a URL without the anchor from the web server. The web servers gets only the part you see in logs. For '/Doc.html#case1' the web server will receive a request for '/Doc.html'. The anchor is used by the bro

Re: map problem : how to debug it ?

Hello Gilles, A browser won't send URL postion after the '#' mark to a web server. So your maps won't work as expected and there is nothing to do in Nginx about it. Regards, Igor. On 12.04.2022 10:16, gperrot wrote: Hello, I am using nginx/1.16.1 on CentOS Linux 7. I am using map directive

Re: NJS FastCGI Response Filtering

Hello Lance, While I'm not 100% sure is there a chance that the reply is gzipped? May be resetting acccept-encoding header would help? Regards, Igor On 17.02.2022 05:02, Lance Dockins wrote: Is there a good way to reliably filter the response body from a FastCGI script via NJS?  I’ve done th