As already said, in this case the work nginx is willing to do is
no different from other workloads, such as with normal HTTP/2
requests or HTTP/1.x requests. As such, nginx is not considered
to be affected by this issue.
>
>
> Thomas
>
> -Original Message-----
> From
27;t mean "fixed" or "not affected" in the strictest
interpretation of languages and what means what.
Thomas
-Original Message-
From: nginx-devel On Behalf Of Maxim Dounin
Sent: Tuesday, October 10, 2023 8:53 AM
To: nginx-devel@nginx.org
Subject: Re: [PATCH] HTTP/
Hello!
On Tue, Oct 10, 2023 at 04:46:04PM +0400, Sergey Kandaurov wrote:
>
> > On 10 Oct 2023, at 16:29, Maxim Dounin wrote:
> >
> > # HG changeset patch
> > # User Maxim Dounin
> > # Date 1696940019 -10800
> > # Tue Oct 10 15:13:39 2023 +0300
> > # Node ID cdda286c0f1b4b10f30d4eb6a63fef
Hello!
On Tue, Oct 10, 2023 at 03:29:02PM +0300, Maxim Dounin wrote:
> # HG changeset patch
> # User Maxim Dounin
> # Date 1696940019 -10800
> # Tue Oct 10 15:13:39 2023 +0300
> # Node ID cdda286c0f1b4b10f30d4eb6a63fefb9b8708ecc
> # Parent 3db945fda515014d220151046d02f3960bcfca0a
> HTTP/2:
> On 10 Oct 2023, at 16:29, Maxim Dounin wrote:
>
> # HG changeset patch
> # User Maxim Dounin
> # Date 1696940019 -10800
> # Tue Oct 10 15:13:39 2023 +0300
> # Node ID cdda286c0f1b4b10f30d4eb6a63fefb9b8708ecc
> # Parent 3db945fda515014d220151046d02f3960bcfca0a
> HTTP/2: per-iteration str