Re: [PATCH 1 of 3] Stream: socket peek in preread phase

2023-12-12 Thread Sergey Kandaurov
> On 10 Nov 2023, at 14:07, Roman Arutyunyan wrote: > > # HG changeset patch > # User Roman Arutyunyan > # Date 1699456644 -14400 > # Wed Nov 08 19:17:24 2023 +0400 > # Node ID 966331bb4936888ef2f034aa2700c130514d0b57 > # Parent 7ec761f0365f418511e30b82e9adf80bc56681df > Stream: socket pe

[nginx] QUIC: avoid partial expansion of PATH_CHALLENGE/PATH_RESPONSE.

2023-12-12 Thread Roman Arutyunyan
details: https://hg.nginx.org/nginx/rev/fcec773dd249 branches: changeset: 9189:fcec773dd249 user: Roman Arutyunyan date: Wed Nov 29 18:13:25 2023 +0400 description: QUIC: avoid partial expansion of PATH_CHALLENGE/PATH_RESPONSE. By default packets with these frames are expanded to 12

[nginx] QUIC: fixed anti-amplification with explicit send.

2023-12-12 Thread Roman Arutyunyan
details: https://hg.nginx.org/nginx/rev/3a67dd34b6cc branches: changeset: 9190:3a67dd34b6cc user: Roman Arutyunyan date: Wed Nov 22 14:52:21 2023 +0400 description: QUIC: fixed anti-amplification with explicit send. Previously, when using ngx_quic_frame_sendto() to explicitly send a

[nginx] QUIC: ignore duplicate PATH_CHALLENGE frames.

2023-12-12 Thread Roman Arutyunyan
details: https://hg.nginx.org/nginx/rev/618132842e7c branches: changeset: 9191:618132842e7c user: Roman Arutyunyan date: Wed Nov 22 14:48:12 2023 +0400 description: QUIC: ignore duplicate PATH_CHALLENGE frames. According to RFC 9000, an endpoint SHOULD NOT send multiple PATH_CHALLEN

[nginx] QUIC: congestion control in ngx_quic_frame_sendto().

2023-12-12 Thread Roman Arutyunyan
details: https://hg.nginx.org/nginx/rev/efcdaa66df2e branches: changeset: 9192:efcdaa66df2e user: Roman Arutyunyan date: Wed Nov 29 21:41:29 2023 +0400 description: QUIC: congestion control in ngx_quic_frame_sendto(). Previously ngx_quic_frame_sendto() ignored congestion control and

[nginx] QUIC: path revalidation after expansion failure.

2023-12-12 Thread Roman Arutyunyan
details: https://hg.nginx.org/nginx/rev/a6f79f044de5 branches: changeset: 9194:a6f79f044de5 user: Roman Arutyunyan date: Wed Nov 29 10:58:21 2023 +0400 description: QUIC: path revalidation after expansion failure. As per RFC 9000, Section 8.2.1: When an endpoint is unable to ex

[nginx] QUIC: ngx_quic_frame_t time fields cleanup.

2023-12-12 Thread Roman Arutyunyan
details: https://hg.nginx.org/nginx/rev/ce1ff81e9b92 branches: changeset: 9193:ce1ff81e9b92 user: Roman Arutyunyan date: Thu Nov 30 15:03:06 2023 +0400 description: QUIC: ngx_quic_frame_t time fields cleanup. The field "first" is removed. It's unused since 909b989ec088. The field "

Re: [PATCH] Linux packages: actualized supported Alpine Linux versions

2023-12-12 Thread Sergey Kandaurov
> On 12 Dec 2023, at 05:45, Konstantin Pavlov wrote: > > # HG changeset patch > # User Konstantin Pavlov > # Date 1702345379 28800 > # Mon Dec 11 17:42:59 2023 -0800 > # Node ID 55f8ce8a8cb0acf9b360e47fd5d0023f16451a80 > # Parent 08533e33d0744bd27bc42d87c47607399903eae5 > Linux packages:

[nginx] QUIC: reset RTT estimator for the new path.

2023-12-12 Thread Sergey Kandaurov
details: https://hg.nginx.org/nginx/rev/ff452f283aa9 branches: changeset: 9195:ff452f283aa9 user: Sergey Kandaurov date: Tue Dec 12 20:20:51 2023 +0400 description: QUIC: reset RTT estimator for the new path. RTT is a property of the path, it must be reset on confirming a peer's own

[nginx] QUIC: path aware in-flight bytes accounting.

2023-12-12 Thread Sergey Kandaurov
details: https://hg.nginx.org/nginx/rev/6c8595b77e66 branches: changeset: 9196:6c8595b77e66 user: Sergey Kandaurov date: Tue Dec 12 20:21:12 2023 +0400 description: QUIC: path aware in-flight bytes accounting. On-packet acknowledgement is made path aware, as per RFC 9000, Section 9.

Re: [PATCH] Added asm ISB as asm pause for ngx_cpu_pause() for aarch64

2023-12-12 Thread Maxim Dounin
Hello! On Mon, Dec 11, 2023 at 05:09:17PM -0600, Julio Suarez wrote: > Hi Maxim, > > > Nitpicking: Added ISB as ngx_cpu_pause() for aarch64. > > Yes, we can make that change. > > > Could you please clarify what do you mean by "a bug"? An empty > > ngx_cpu_pause() is certainly not a bug, it's

processing a request without body

2023-12-12 Thread Muhammad Nuzaihan
Hi, I need to process requests with only URI path (without body) for a module. It seems ngx_http_request_body_filter_pt is *not* executed whenever there is a request without a body (it looked like it bypassed without request body) and only ngx_http_output_body_filter_pt part of the code is execu