Inquiry about QUIC Congestion Control Algorithms Development

Hi, I've been following the development of the QUIC protocol within Nginx, and I am particularly interested in the implementation of advanced congestion control algorithms such as BBR and CUBIC. Considering the impact that these algorithms can have on network performance, especially in

NGINX multiple authentication methods (one or the other) AND an IP check seems impossible

``` location / { proxy_pass $forward_auth_target; allow x/24; deny all; satisfy any; # This gets satisfied by the IP check, and auth is completely bypassed auth_basic ""; auth_basic_user_file "/etc/nginx/basic_auth/$forward_auth_bypass";

[njs] Fetch: fixed heap-buffer-overflow in Headers.get().

details: https://hg.nginx.org/njs/rev/f75f670905f0 branches: changeset: 2339:f75f670905f0 user: Dmitry Volyntsev date: Thu May 23 22:50:34 2024 -0700 description: Fetch: fixed heap-buffer-overflow in Headers.get(). Previously, when more than one header with the same name added to a

[njs] Added fast path in njs_chb_utf8_length() for ASCII input.

details: https://hg.nginx.org/njs/rev/437fc09db765 branches: changeset: 2338:437fc09db765 user: Dmitry Volyntsev date: Thu May 23 22:50:19 2024 -0700 description: Added fast path in njs_chb_utf8_length() for ASCII input. diffstat: src/njs_chb.h| 19

[PATCH] Add $upstream_cache_key

Greetings, Here is a patch that exposes the constructed cache key as $upstream_cache_key variable. Sometimes it's quite useful when debugging complicated setups and fighting some typos. I've attached two patches: 1. from me to add that variable 2. from Maxim Dounin to update docs -- wbr,

[njs] Fixed retval handling after an exception.

details: https://hg.nginx.org/njs/rev/585756e8cafe branches: changeset: 2337:585756e8cafe user: Dmitry Volyntsev date: Wed May 22 23:08:15 2024 -0700 description: Fixed retval handling after an exception. Previously, some functions set a retval too early. If this happened before

Re: I think I found a fix for the memory leak issue on gRPC module

Hi, On Wed, May 22, 2024 at 06:14:26PM +0400, Roman Arutyunyan wrote: > Hi, > > Indeed there's a problem there. We have similar problems in other places as > well. Attached is a patch that fixes all I could find. > > I did some testing for the sub_filter with the following config. Small >

[njs] Improved String.prototype.replaceAll() for readability.

details: https://hg.nginx.org/njs/rev/077a5b2f30d8 branches: changeset: 2336:077a5b2f30d8 user: Dmitry Volyntsev date: Wed May 22 17:26:16 2024 -0700 description: Improved String.prototype.replaceAll() for readability. diffstat: src/njs_string.c | 44

[njs] Fixed String.prototype.replaceAll() with zero length argument.

details: https://hg.nginx.org/njs/rev/e496851c0fe7 branches: changeset: 2335:e496851c0fe7 user: Dmitry Volyntsev date: Wed May 22 17:26:08 2024 -0700 description: Fixed String.prototype.replaceAll() with zero length argument. This fixes #712 issue on Github. diffstat:

[njs] Aligned StringIndexOf() implementation with the spec.

details: https://hg.nginx.org/njs/rev/bc09b884022d branches: changeset: 2334:bc09b884022d user: Dmitry Volyntsev date: Tue May 21 23:41:10 2024 -0700 description: Aligned StringIndexOf() implementation with the spec. When searchValue is empty the function should return early when

[njs] Removed code for byte strings in built-in functions.

details: https://hg.nginx.org/njs/rev/2d098d2a1c85 branches: changeset: 2333:2d098d2a1c85 user: Dmitry Volyntsev date: Tue May 21 23:41:10 2024 -0700 description: Removed code for byte strings in built-in functions. diffstat: src/njs_array.c | 52

[njs] Avoid creating byte strings explicitly.

details: https://hg.nginx.org/njs/rev/27da19960b72 branches: changeset: 2332:27da19960b72 user: Dmitry Volyntsev date: Tue May 21 23:38:19 2024 -0700 description: Avoid creating byte strings explicitly. Previously, calls like njs_string_new(,,,0) produced byte strings by explicitly

Re: I think I found a fix for the memory leak issue on gRPC module

Hi, Indeed there's a problem there. We have similar problems in other places as well. Attached is a patch that fixes all I could find. I did some testing for the sub_filter with the following config. Small buffers exaggerate the problem. http { server { listen 8000;

SVN front-end using Nginx?

Hi Everyone, I'd like to use SVN, and Nginx as the web server for it. From what I've found, it looks like Apache is required due to mod_dav_svn (and the combo is Apache with Nginx proxy). I also came across svnserve, but I am not familiar with it. Is anyone aware of a way to use a pure Nginx

[nginx] Configure: fixed building libatomic test.

details: https://hg.nginx.org/nginx/rev/f58b6f636238 branches: changeset: 9247:f58b6f636238 user: Edgar Bonet date: Thu May 16 11:15:10 2024 +0200 description: Configure: fixed building libatomic test. Using "long *" instead of "AO_t *" leads either to -Wincompatible-pointer-types

[njs] HTTP: fixed handling of 0 length request body.

details: https://hg.nginx.org/njs/rev/286dbef3c0b2 branches: changeset: 2331:286dbef3c0b2 user: Dmitry Volyntsev date: Mon May 20 16:44:10 2024 -0700 description: HTTP: fixed handling of 0 length request body. Previously, when r.requestBuffer was passed as a body argument to

Re: [PATCH] Fix compile error in configure script

Hello! On 2024-05-20, Sergey Kandaurov wrote: > Concerning type compatibility, C11 gives a definition on what types > are compatible. [...] Thank-you for sharing these findings! > I like the patch, but would like to adjust the commit log: > there some styles issues and over-quoting. Also,

Re: [PATCH] Fix compile error in configure script

On Sat, May 18, 2024 at 02:43:52PM +0200, Edgar Bonet wrote: > Hello! > > Yesterday, I wrote: > > My understanding is that the compiler considers 'int' and 'long' to be > > incompatible types [... On ILP32,] 'size_t' being an 'unsigned int', > > it is incompatible with 'long'. > > > > On LP64

Re: Twitter incompatibility

Fixed, many thanks. I had asked ChatGPT 4o and it could not help. On Sun, May 19, 2024 at 6:28 PM J Carter wrote: > > Hello, > > On Sun, 19 May 2024 16:47:02 -0400 > Saint Michael wrote: > > > I need some help with a Nginx,. Twitter problem > > please open a twitter client x.com > > and post

Re: Twitter incompatibility

Hello, On Sun, 19 May 2024 16:47:02 -0400 Saint Michael wrote: > I need some help with a Nginx,. Twitter problem > please open a twitter client x.com > and post this link > https://patrician.org/22a51cfb-7d5b-4a97-a687-a10cd1946766/ > and then open a new client and post >

Twitter incompatibility

I need some help with a Nginx,. Twitter problem please open a twitter client x.com and post this link https://patrician.org/22a51cfb-7d5b-4a97-a687-a10cd1946766/ and then open a new client and post https://xlong.org/p/a3622727-4df1-46f3-aee8-ee0a43194906/ in the first case, it's an Apache server,

Re: [PATCH] Fix compile error in configure script

Hello! Yesterday, I wrote: > My understanding is that the compiler considers 'int' and 'long' to be > incompatible types [... On ILP32,] 'size_t' being an 'unsigned int', > it is incompatible with 'long'. > > On LP64 (your typical 64-bit Linux/Mac), 'size_t' is a 'unsigned > long', which is

[njs] Removing njs_string_set() from builtin functions.

details: https://hg.nginx.org/njs/rev/8851a78723dc branches: changeset: 2330:8851a78723dc user: Dmitry Volyntsev date: Fri May 17 21:54:50 2024 -0700 description: Removing njs_string_set() from builtin functions. This is the last function that produced byte strings. diffstat:

[njs] Change: removed byte strings API.

details: https://hg.nginx.org/njs/rev/4e0553f7ea68 branches: changeset: 2329:4e0553f7ea68 user: Dmitry Volyntsev date: Fri May 17 21:54:50 2024 -0700 description: Change: removed byte strings API. These functions are unsafe because they produce byte strings. Byte strings may not

[njs] Optimized string creation with ASCII input.

details: https://hg.nginx.org/njs/rev/dec46ad52e9a branches: changeset: 2328:dec46ad52e9a user: Dmitry Volyntsev date: Fri May 17 21:54:49 2024 -0700 description: Optimized string creation with ASCII input. diffstat: src/njs_string.c | 12 1 files changed, 12

[njs] Added string creation benchmark.

details: https://hg.nginx.org/njs/rev/f474755a4dce branches: changeset: 2327:f474755a4dce user: Dmitry Volyntsev date: Fri May 17 18:36:12 2024 -0700 description: Added string creation benchmark. diffstat: src/test/njs_benchmark.c | 159

Re: nginx configured as loadbalancer returning 404 not found

On Fri, May 17, 2024 at 7:39 PM Sergey A. Osokin wrote: > Hi Kaushal, > > On Fri, May 17, 2024 at 04:49:59PM +0530, Kaushal Shriyan wrote: > > > > I am running nginx version 1.26 on "Ubuntu 22.04.4 LTS" I have configured > > the nginx as load balancer and the configuration details are as follows

Re: [PATCH] Fix compile error in configure script

Hello! Sergey Kandaurov wrote: > > objs/autotest.c:9:48: error: passing argument 1 > > of 'AO_compare_and_swap' from incompatible pointer type > > [-Wincompatible-pointer-types] > > Where did you try to build? I experienced this when building for arm and i686, both cross-compiled from x86_64.

Re: [PATCH] Fix compile error in configure script

> On 16 May 2024, at 13:25, Edgar Bonet wrote: > > # HG changeset patch > # User Edgar Bonet > # Date 1715850910 -7200 > # Thu May 16 11:15:10 2024 +0200 > # Node ID c2c3b0d74b1a7d3f967421c72760b5c573afcd81 > # Parent 89093b003fcb54c7f8dc66042f17bc4dea4e7709 > Fix compile error in

Re: nginx configured as loadbalancer returning 404 not found

Hi Kaushal, On Fri, May 17, 2024 at 04:49:59PM +0530, Kaushal Shriyan wrote: > > I am running nginx version 1.26 on "Ubuntu 22.04.4 LTS" I have configured > the nginx as load balancer and the configuration details are as follows > > # nginx -v > nginx version: nginx/1.26.0 > # > > server {

nginx configured as loadbalancer returning 404 not found

Hi, I am running nginx version 1.26 on "Ubuntu 22.04.4 LTS" I have configured the nginx as load balancer and the configuration details are as follows # nginx -v nginx version: nginx/1.26.0 # server { listen 8085; #server_name 172.30.2.11; server name 210.11.1.110;

Re: Status code 0

Hello Just to close that conversation, it seems this was an error of our devops in charge of alerting, who was using curl in a bad way. Best regards, Sébastien Le lun. 6 mai 2024 à 11:33, Sébastien Rebecchi a écrit : > Hello! > > There is nothing regarding this issue in nginx logs. > > Now I

[PATCH] Fix compile error in configure script

# HG changeset patch # User Edgar Bonet # Date 1715850910 -7200 # Thu May 16 11:15:10 2024 +0200 # Node ID c2c3b0d74b1a7d3f967421c72760b5c573afcd81 # Parent 89093b003fcb54c7f8dc66042f17bc4dea4e7709 Fix compile error in configure script Building with GCC 14 fails at the configure step with:

Re: limiting number of HTTP request headers

Hi max, If you use njs, then you can use `r.headersIn` or `r.rawHeadersIn` https://nginx.org/en/docs/njs/reference.html#r_headers_in https://nginx.org/en/docs/njs/reference.html#r_raw_headers_in Regards, Liu Maksim Yevmenkin 于2024年5月16日周四 08:28写道： > > Hello! > > Could the community share their

limiting number of HTTP request headers

Hello! Could the community share their thoughts on introducing a directive to cap the number of HTTP request headers? While we currently have the ability to limit client HTTP request buffer size, having more specific control over the number of headers could be advantageous. Thanks, max

How to configure HTTP CONNECT to SSH Proxy?

Dear NGINX Mailing list,   I'm a user of https://github.com/proxytunnel/proxytunnel to connect to SSH over HTTPS. This requires the HTTP server to redirect the traffic to a local SSH server.   Following http://dag.wiee.rs/howto/ssh-http-tunneling/ I implemented this on my server using Apache.

Discussion: websocket over http2 / http3?

Hi, websocket over http2 is defined in RFC8441, chrome and firefox support it. https://chromestatus.com/feature/6251293127475200 websocket over http3 is defined in RFC9220, neither of chrome nor firefox support it. https://chromestatus.com/feature/5080537855688704 Is there any plan to support

Re: [patch] reject http header without colon (:) in the header name

> nginx is about as popular as GWS, same reasoning might be considered. What I'm saying is exceptional about GWS is not its popularity. Of course, Nginx (and Apache) are similarly popular. I'm arguing that because GWS is by design a single-purpose web server that serves the interest of a single

Re: [patch] reject http header without colon (:) in the header name

nginx is about as popular as GWS, same reasoning might be considered. btw, do you suggest to 1) introduce new behaviour by some setting (default is unchanged) 2) change default behaviour ? and I'm quite curious why do you want to change current behaviour пн, 13 мая 2024 г. в 16:30, Ben Kallus

Re: [patch] reject http header without colon (:) in the header name

Okay; I should have been more specific. I meant that nginx is unique among *general-purpose* web servers. GWS is something of an special case; it also accepts requests with no Host header, and doesn't validate the version string (e.g., HTTP/1.9 is accepted). Google has opted into these

nginx.org repo now on GitHub

A small announcement to say that the sources for the nginx.org website are now maintained on GitHub: https://github.com/nginx/nginx.org Issues and PRs are open so please feel free to make suggestions and/or propose changes. Cheers, Liam. ___ nginx

Re: [patch] reject http header without colon (:) in the header name

Hi, On Tue, May 07, 2024 at 05:58:34PM -0400, Ben Kallus wrote: > Nginx is the only widely-used HTTP server that ignores invalid > field-lines. This behavior makes it trivial to fingerprint. A simple test shows that google server gws does the same. > I never reported this in the past because I

[njs] Configure: fixed QuickJS detection with --with-quickjs flag.

details: https://hg.nginx.org/njs/rev/02369792b032 branches: changeset: 2326:02369792b032 user: Dmitry Volyntsev date: Thu May 09 12:58:57 2024 -0700 description: Configure: fixed QuickJS detection with --with-quickjs flag. diffstat: auto/quickjs | 2 +- 1 files changed, 1

Re: Bypass cache if PHPSESSID exists

On Thu, 09 May 2024 18:11:18 +0100, Christos Chatzaras wrote: > > if ($http_cookie ~* "_mcnc|PHPSESSID") { > set $no_cache "1"; > } > Try to use map instead if. -- wbr, Kirill ___ nginx mailing list

Bypass cache if PHPSESSID exists

Hello, I want to bypass cache if PHPSESSID exists. I have this configuration: http { fastcgi_cache_path /tmpfs/cache levels=1:2 keys_zone=fastcgicache:10m inactive=10m max_size=1024m; fastcgi_cache_key $device_type$scheme$request_method$host$request_uri;

Re: [patch] reject http header without colon (:) in the header name

Nginx is the only widely-used HTTP server that ignores invalid field-lines. This behavior makes it trivial to fingerprint. I never reported this in the past because I assumed Maxim wouldn't care about that sort of thing. Now that he's out of the picture, maybe others will see things differently?

[patch] reject http header without colon (:) in the header name

hello, it appears that nginx would happily accept http header without colon (:) in the header name. the patch below tries to address this. thanks max == --- a/ports/netflix/nginx/files/nginx/src/http/ngx_http_parse.c +++ b/ports/netflix/nginx/files/nginx/src/http/ngx_http_parse.c @@ -941,14

[PATCH] Tests: ssl_engine_keys.t improved

# HG changeset patch # User Oksana Deeva # Date 1715111756 -10800 # Tue May 07 22:55:56 2024 +0300 # Node ID e5014b423e1391dd1078d064361a0b28d1a488d0 # Parent 2a607a31f583add7adfa1ac434a3f793d327ca6b Tests: ssl_engine_keys.t improved diff -r 2a607a31f583 -r e5014b423e13 ssl_engine_keys.t

Eprints (using PERL CGI)over NGINX reverse proxy

Good day! We have Institutional Repository that is made with the use of Eprints, It has no problem uploading file up to 1 gb as default when in local access. but when we use NGINX as the reverse proxy it only accept up to 128 kb file. Does PERL CGI affects the upload limit over NGINX? we

Re: Status code 0

Hello! There is nothing regarding this issue in nginx logs. Now I think the issue is not with nginx itself, but in front of nginx, with Linux itself. We monitor using curl, and it seems that curl can print status code 0 when it can not establish a connection with the server. I think the Linux

Re: [PATCH]HTTP/2 connection not properly closing during graceful shutdown

Hello, Thanks for your confirmation and explanations. The following is a modified patch. In my test it would send GOAWAY(on stream id 0), same as the previous one, but call ngx_http_v2_finalize_connection instead of set c->close. # HG changeset patch # User Kasei Wang # Date 1714965008 -28800

Re: Status code 0

Hello! On Sat, May 04, 2024 at 07:31:43PM +0200, Sébastien Rebecchi wrote: > Hello > > What does it mean when nginx returns an http status code 0? > > We see that cause we monitor nginx response status code, which is used as > front of our apps. The apps themselves can not return 0, only 200

Re: Status code 0

Hi Sébastien, thanks for the report. On Sat, May 04, 2024 at 07:31:43PM +0200, Sébastien Rebecchi wrote: > > What does it mean when nginx returns an http status code 0? > > We see that cause we monitor nginx response status code, which is used as > front of our apps. The apps themselves can

Status code 0

Hello What does it mean when nginx returns an http status code 0? We see that cause we monitor nginx response status code, which is used as front of our apps. The apps themselves can not return 0, only 200 or 500. So it seems issue here comes from nginx itself which can not process the

Re: [PATCH] Stream pass: disabled passing from or to udp

> On 3 May 2024, at 20:30, Roman Arutyunyan wrote: > > Hi, > > On Fri, May 03, 2024 at 08:24:16PM +0400, Sergey Kandaurov wrote: >> >>> On 26 Apr 2024, at 15:15, Roman Arutyunyan wrote: >>> >>> # HG changeset patch >>> # User Roman Arutyunyan >>> # Date 1714057362 -14400 >>> # Thu Apr

[nginx] Stream pass: disabled passing from or to udp.

details: https://hg.nginx.org/nginx/rev/89093b003fcb branches: changeset: 9246:89093b003fcb user: Roman Arutyunyan date: Fri May 03 20:26:05 2024 +0400 description: Stream pass: disabled passing from or to udp. Passing from udp was not possible for the most part due to preread

Re: [PATCH] Stream pass: disabled passing from or to udp

Hi, On Fri, May 03, 2024 at 08:24:16PM +0400, Sergey Kandaurov wrote: > > > On 26 Apr 2024, at 15:15, Roman Arutyunyan wrote: > > > > # HG changeset patch > > # User Roman Arutyunyan > > # Date 1714057362 -14400 > > # Thu Apr 25 19:02:42 2024 +0400 > > # Branch stable-1.26 > > wrong

[nginx] SSL: fixed possible configuration overwrite loading "engine:" keys.

details: https://hg.nginx.org/nginx/rev/c4792b0f1976 branches: changeset: 9245:c4792b0f1976 user: Sergey Kandaurov date: Fri May 03 20:29:01 2024 +0400 description: SSL: fixed possible configuration overwrite loading "engine:" keys. When loading certificate keys via

[nginx] HTTP/3: fixed handling of malformed request body length.

details: https://hg.nginx.org/nginx/rev/690f46d3bc1f branches: changeset: 9244:690f46d3bc1f user: Sergey Kandaurov date: Fri May 03 20:28:32 2024 +0400 description: HTTP/3: fixed handling of malformed request body length. Previously, a request body larger than declared in

[nginx] Version bump.

details: https://hg.nginx.org/nginx/rev/ff0312de0112 branches: changeset: 9243:ff0312de0112 user: Sergey Kandaurov date: Fri May 03 20:28:22 2024 +0400 description: Version bump. diffstat: src/core/nginx.h | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diffs (14

Re: [PATCH] Stream pass: disabled passing from or to udp

> On 26 Apr 2024, at 15:15, Roman Arutyunyan wrote: > > # HG changeset patch > # User Roman Arutyunyan > # Date 1714057362 -14400 > # Thu Apr 25 19:02:42 2024 +0400 > # Branch stable-1.26 wrong branch > # Node ID a60cd9c99efcc1204e6d395104beb39883308c93 > # Parent

Re: [PATCH] SSL: fixed possible configuration overwrite loading "engine:" keys

Hi, On Fri, May 03, 2024 at 04:28:17AM +0400, Sergey Kandaurov wrote: > # HG changeset patch > # User Sergey Kandaurov > # Date 1714670294 -14400 > # Thu May 02 21:18:14 2024 +0400 > # Node ID e00aeabf2b29b891891fd150a01c82b0763c57c0 > # Parent 49dce50fad40bf09db81ca2a35983ecd7b740e43 >

[PATCH] SSL: fixed possible configuration overwrite loading "engine:" keys

# HG changeset patch # User Sergey Kandaurov # Date 1714670294 -14400 # Thu May 02 21:18:14 2024 +0400 # Node ID e00aeabf2b29b891891fd150a01c82b0763c57c0 # Parent 49dce50fad40bf09db81ca2a35983ecd7b740e43 SSL: fixed possible configuration overwrite loading "engine:" keys. When loading

[PATCH] Configure: increase the default optimization level to -O2

# HG changeset patch # User Piotr Sikora # Date 1714589900 0 # Wed May 01 18:58:20 2024 + # Node ID 429191aad8d3ab8f70d40dfdd7684a256357bc48 # Parent 49dce50fad40bf09db81ca2a35983ecd7b740e43 Configure: increase the default optimization level to -O2. Signed-off-by: Piotr Sikora diff

[PATCH] Configure: postpone running the test binary

# HG changeset patch # User Piotr Sikora # Date 1714589827 0 # Wed May 01 18:57:07 2024 + # Node ID 2d5e754e3a4e7a59eaf7f653ad4fd5346f53eab4 # Parent 49dce50fad40bf09db81ca2a35983ecd7b740e43 Configure: postpone running the test binary. Previously, the ./configure script would attempt

[PATCH] Configure: build C++ test module using C++ compiler

# HG changeset patch # User Piotr Sikora # Date 1714589815 0 # Wed May 01 18:56:55 2024 + # Node ID 787e1adea9aa7f681884657f119e864af0be3e0d # Parent 49dce50fad40bf09db81ca2a35983ecd7b740e43 Configure: build C++ test module using C++ compiler. This fixes build when using C compiler

[PATCH] Configure: fix build on Windows using non-MSVC compilers

# HG changeset patch # User Piotr Sikora # Date 1714589717 0 # Wed May 01 18:55:17 2024 + # Node ID 43b04ece77b7132db868122a20c99c8ba89adfb5 # Parent 49dce50fad40bf09db81ca2a35983ecd7b740e43 Configure: fix build on Windows using non-MSVC compilers. Previously, kernel32 and user32

[PATCH] Configure: always test with provided C compiler options

# HG changeset patch # User Piotr Sikora # Date 1714589692 0 # Wed May 01 18:54:52 2024 + # Node ID df39b5d3c3a0c670f3d94e623351b6c659f5be84 # Parent 49dce50fad40bf09db81ca2a35983ecd7b740e43 Configure: always test with provided C compiler options. Previously, build in auto/include

[PATCH] Configure: fix warnings in a few feature tests

# HG changeset patch # User Piotr Sikora # Date 1714589586 0 # Wed May 01 18:53:06 2024 + # Node ID c083cd8ead811426c6f7bd7c4ab58a413d80be52 # Parent 49dce50fad40bf09db81ca2a35983ecd7b740e43 Configure: fix warnings in a few feature tests. Signed-off-by: Piotr Sikora diff -r

[PATCH] Configure: test --with-cc-opt options

# HG changeset patch # User Piotr Sikora # Date 1714589524 0 # Wed May 01 18:52:04 2024 + # Node ID 0d5498e86bf8a7f119ed83dbc0789be37d728334 # Parent 49dce50fad40bf09db81ca2a35983ecd7b740e43 Configure: test --with-cc-opt options. Previously, invalid C compiler options would fail with

[PATCH] QUIC: fix build against musl-libc when using Clang

# HG changeset patch # User Piotr Sikora # Date 1714589495 0 # Wed May 01 18:51:35 2024 + # Node ID 962cddbaecf02b9c213dca492a74b23924b8f24c # Parent 49dce50fad40bf09db81ca2a35983ecd7b740e43 QUIC: fix build against musl-libc when using Clang. Signed-off-by: Piotr Sikora diff -r

[njs] QuickJS: added zlib module.

details: https://hg.nginx.org/njs/rev/f146b5dc21cc branches: changeset: 2325:f146b5dc21cc user: Dmitry Volyntsev date: Wed May 01 17:31:01 2024 -0700 description: QuickJS: added zlib module. diffstat: auto/init | 1 + auto/make |42 +-

Re: I need help with our NGINX set up

We dont use PHP, our system use perl cgi. So the problem is in cgi? On Wed, May 1, 2024, 8:57 AM Dan Swaney wrote: > The clue is with the URL which failed. > > From first look, you appear to be using a FAST CGI URL with PHP? > > Just a wild guess, but try using: > ``` > > fastcgi_param

Re: I need help with our NGINX set up

The clue is with the URL which failed. >From first look, you appear to be using a FAST CGI URL with PHP? Just a wild guess, but try using: ``` fastcgi_param PHP_VALUE "upload_max_filesize = 500M \n post_max_size=500M" ``` Here is a reference link mentioning it:

Re: [PATCH]HTTP/2 connection not properly closing during graceful shutdown

Hi, On Tue, Apr 23, 2024 at 06:02:08PM +0800, Kasei Wang wrote: > Hello, > > I found that there is a slight probability of HTTP/2 connections not > properly closing during graceful shutdown, leading to worker processes > in shutting down state remaining stuck for an extended period. After >

[njs] Tests: fixed typo in stream_js_dup_set.t introduced in be271e8d0b3b.

details: https://hg.nginx.org/njs/rev/18fc657411ca branches: changeset: 2324:18fc657411ca user: Dmitry Volyntsev date: Fri Apr 26 16:48:19 2024 -0700 description: Tests: fixed typo in stream_js_dup_set.t introduced in be271e8d0b3b. Previously, with typo the test was always skipped.

[njs] Fetch: fixed request Host header when the port is non-standard.

details: https://hg.nginx.org/njs/rev/7456fe29ac0a branches: changeset: 2323:7456fe29ac0a user: Dmitry Volyntsev date: Fri Apr 26 16:48:17 2024 -0700 description: Fetch: fixed request Host header when the port is non-standard. This fixes #707 issue on Github. diffstat:

[njs] Allowing to use custom allocator in njs_chb_t.

details: https://hg.nginx.org/njs/rev/622387b5b612 branches: changeset: 2322:622387b5b612 user: Dmitry Volyntsev date: Fri Apr 26 16:27:52 2024 -0700 description: Allowing to use custom allocator in njs_chb_t. diffstat: external/njs_query_string_module.c | 6 +++---

Re: headers do not work

Hi, On Fri, Apr 26, 2024 at 05:19:48PM -0400, Saint Michael wrote: > I am not using openresty as a proxy but as a web server. Twitter > requests an image, and it sends the HTTP request with header > "Finagle-Ctx-com.twitter.finagle." This makes nginx abort the > operation. > I need the operation

Re: [PATCH] proxy_cache_lock: Make lock timer configurable

Any update on getting this PR merged? I'm also facing the same issue > On 21 Mar 2024, at 08:30, Nejc Lovrencic wrote: > > # HG changeset patch > # User Nejc Lovrencic > # Date 1711005111 -3600 > # Thu Mar 21 08:11:51 2024 +0100 > # Node ID 8d38e6642e82bb219bb5b586f1dcca5222a036e8 > #

Re: headers do not work

I am not using openresty as a proxy but as a web server. Twitter requests an image, and it sends the HTTP request with header "Finagle-Ctx-com.twitter.finagle." This makes nginx abort the operation. I need the operation to be completed as designed. For that, I added underscores_in_headers (on or

Re: headers do not work

Hi, > On 25 Apr 2024, at 8:10 AM, Saint Michael wrote: > > I keep getting this error > *356 client sent invalid header line: > "Finagle-Ctx-com.twitter.finagle.Retries: 0" while reading client > request headers, and twitter cannot read my twitter-card > yet, I do have > underscores_in_headers

[PATCH] Stream pass: disabled passing from or to udp

# HG changeset patch # User Roman Arutyunyan # Date 1714057362 -14400 # Thu Apr 25 19:02:42 2024 +0400 # Branch stable-1.26 # Node ID a60cd9c99efcc1204e6d395104beb39883308c93 # Parent cdf74ac25b47ec928b53aa82ccc1c3d288a2f81c Stream pass: disabled passing from or to udp. Passing from udp

Re: Leaky NGINX Plugin Advice

Hello, As this is a development-related question, a better list for it is nginx-devel@nginx.org . > On 23 Apr 2024, at 1:40 PM, Alex Hussein-Kershaw (HE/HIM) via nginx > wrote: > > Hi Folks, > > I've inherited an nginx plugin, written against 0.7.69 that has

Re: QUIC: use sendmmsg() with GSO

Hi, > On 20 Apr 2024, at 6:12 PM, Marcin Wanat wrote: > > Hi, > > I discovered a patch for QUIC that enables the use of sendmmsg() with > GSO, authored by Roman Arutyunyan: > > https://mailman.nginx.org/pipermail/nginx-devel/2023-July/4ZTXGDMY2LC4VRZRBNBXGULYHS5DMR3Z.html > > However, for

Re: [PROPOSAL]: Extend list of Stream phases

Hi Andrey, > On 11 Apr 2024, at 3:27 AM, Andrey Kulikov wrote: > > Hello, > > Consider the following test-case: > I, as admin, would like to limit access to certain resources, based on Client > TLS certificate content, fields, etc... > > Solution for HTTP: Easy! > There is

headers do not work

I keep getting this error *356 client sent invalid header line: "Finagle-Ctx-com.twitter.finagle.Retries: 0" while reading client request headers, and twitter cannot read my twitter-card yet, I do have underscores_in_headers on; ignore_invalid_headers on; in the http{} block How do I force nginx

Re: merge_slashes

Добрый день, > On 16 Apr 2024, at 11:41 PM, Vladimir Sopot wrote: > > Здравствуйте! > > Есть примерно такой упрощённый конфиг и при обращении к > some.localsome.html merge_slashes не работает. Если в первом сервере > убрать merge_slashes off, то всё работает нормально и во втором

[nginx-announce] nginx-1.26.0

Changes with nginx 1.26.023 Apr 2024 *) 1.26.x stable branch. Roman Arutyunyan a...@nginx.com ___ nginx-announce mailing list nginx-announce@nginx.org

[nginx-ru-announce] nginx-1.26.0

Изменения в nginx 1.26.0 23.04.2024 *) Стабильная ветка 1.26.x. Roman Arutyunyan a...@nginx.com ___ nginx-ru-announce mailing list nginx-ru-announce@nginx.org

nginx-1.26.0

Изменения в nginx 1.26.0 23.04.2024 *) Стабильная ветка 1.26.x. Roman Arutyunyan a...@nginx.com ___ nginx-ru mailing list nginx-ru@nginx.org https://mailman.nginx.org/mailman/listinfo/nginx-ru

nginx-1.26.0

Changes with nginx 1.26.023 Apr 2024 *) 1.26.x stable branch. Roman Arutyunyan a...@nginx.com ___ nginx mailing list nginx@nginx.org https://mailman.nginx.org/mailman/listinfo/nginx

[nginx] release-1.26.0 tag

details: https://hg.nginx.org/nginx/rev/cdf74ac25b47 branches: stable-1.26 changeset: 9242:cdf74ac25b47 user: Roman Arutyunyan date: Tue Apr 23 18:04:32 2024 +0400 description: release-1.26.0 tag diffstat: .hgtags | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) diffs (8

[nginx] nginx-1.26.0-RELEASE

details: https://hg.nginx.org/nginx/rev/a58202a8c41b branches: stable-1.26 changeset: 9241:a58202a8c41b user: Roman Arutyunyan date: Tue Apr 23 17:40:08 2024 +0400 description: nginx-1.26.0-RELEASE diffstat: docs/xml/nginx/changes.xml | 14 ++ 1 files changed, 14

[nginx] Stable branch.

details: https://hg.nginx.org/nginx/rev/52f427a4c97e branches: stable-1.26 changeset: 9240:52f427a4c97e user: Roman Arutyunyan date: Tue Apr 23 17:31:41 2024 +0400 description: Stable branch. diffstat: src/core/nginx.h | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-)

Re: [PATCH] HTTP/3: fixed handling of malformed request body length

Hi, On Tue, Apr 23, 2024 at 05:14:54PM +0400, Sergey Kandaurov wrote: > > > On 22 Apr 2024, at 19:00, Sergey Kandaurov wrote: > > > > # HG changeset patch > > # User Sergey Kandaurov > > # Date 1713798017 -14400 > > # Mon Apr 22 19:00:17 2024 +0400 > > # Node ID

Re: [PATCH] HTTP/3: fixed handling of malformed request body length

> On 22 Apr 2024, at 19:00, Sergey Kandaurov wrote: > > # HG changeset patch > # User Sergey Kandaurov > # Date 1713798017 -14400 > # Mon Apr 22 19:00:17 2024 +0400 > # Node ID 754e32eaca24ad751e2a94790e1afd55202c1aba > # Parent 9f84f2e49c624e82e054a2dcd48723119c44029c > HTTP/3: fixed

[PATCH]HTTP/2 connection not properly closing during graceful shutdown

Hello, I found that there is a slight probability of HTTP/2 connections not properly closing during graceful shutdown, leading to worker processes in shutting down state remaining stuck for an extended period. After investigation, the issue appears to stem from the following: 1. worker processes

Leaky NGINX Plugin Advice

Hi Folks, I've inherited an nginx plugin, written against 0.7.69 that has recently been moved to use nginx 1.24.0 to resolve the need to ship old versions of openssl. I've found during performance testing that it's leaking file descriptors. After a few hours running and leaking I hit my

[njs] Configure: fixed default path QuickJS discovery typo.

details: https://hg.nginx.org/njs/rev/a97a9f3b3cea branches: changeset: 2321:a97a9f3b3cea user: Dmitry Volyntsev date: Mon Apr 22 18:59:03 2024 -0700 description: Configure: fixed default path QuickJS discovery typo. The issue was introduced in 1c8b6b9bc06c (0.8.4). This closes

  1   2   3   4   5   6   7   8   9   10   >