Thanks again Maxim. Response inlined.
> On Oct 20, 2022, at 6:43 PM, Maxim Dounin <mdou...@mdounin.ru> wrote: > > Hello! > > On Thu, Oct 20, 2022 at 06:09:11PM -0700, Jojy Varghese via nginx-devel wrote: > > [...] > >>> If you think that nginx does something wrong, you may want to >>> elaborate on the details of the incorrect behaviour you observe >>> (as well as why you think it's incorrect, and how would you like >>> to improve it). >> >> We ran into a problem where the connection close (as described >> above) causes some clients (chrome browser) to fail long running >> (large) downloads using h2. This is I think because these >> clients send a WINDOW UPDATE towards the end and Nginx sends a >> TCP RST since the connection is closed. > > So it looks like you are running into the race condition the > lingering close is expected to solve. You may want to upgrade > nginx then. Indeed looks like that :). I think the lingering close should solve the problem/race condition we are seeing. > > Note well that lingering close support in HTTP/2 was added in > nginx 1.19.1, more than two years ago, and the last nginx version > without it is not supported for more than a year. > > -- > Maxim Dounin > http://mdounin.ru/ > _______________________________________________ > nginx-devel mailing list -- nginx-devel@nginx.org > To unsubscribe send an email to nginx-devel-le...@nginx.org _______________________________________________ nginx-devel mailing list -- nginx-devel@nginx.org To unsubscribe send an email to nginx-devel-le...@nginx.org
