Dounin" wrote:
>Hello!
>
>On Wed, Dec 27, 2023 at 08:38:15PM +0800, Jiuzhou Cui wrote:
>
>> Thank you for your reply.
>>
>> Firstly, we meet the problem. And this patch works for me.
>>
>> My scenario is after send response body about 10-20MB, we just
he request begining, we didn't set proxy_buffering = "on" and limit_rate.
At 2023-12-27 19:19:01, "Maxim Dounin" wrote:
>Hello!
>
>On Wed, Dec 27, 2023 at 10:56:44AM +0800, Jiuzhou Cui wrote:
>
>> Hello!
>>
>>
>> # HG changeset patch
Hello!
# HG changeset patch
# User Jiuzhou Cui
# Date 1703645578 -28800
# Wed Dec 27 10:52:58 2023 +0800
# Node ID 474ae07e47272e435d81c0ca9e4867aae35c30ab
# Parent ee40e2b1d0833b46128a357fbc84c6e23be9be07
Don't delete timer of write event when it's delayed.
This will mak
, so maybe error_reason "failed to process transport
parameters" is useful for me to positioning problem. What do you think about
this?
At 2023-02-16 22:42:27, "Sergey Kandaurov" wrote:
>
>> On 16 Feb 2023, at 17:36, Jiuzhou Cui wrote:
>>
>> Hello
Hello!
# HG changeset patch
# User Jiuzhou Cui
# Date 1676554419 -28800
# Thu Feb 16 21:33:39 2023 +0800
# Branch quic
# Node ID 13396c3ad10bdc8c1ac6969e965ceac510dc162f
# Parent b87a0dbc1150f415def5bc1e1f00d02b33519026
QUIC: add error code for handshake failed.
diff -r b87a0dbc1150 -r
Hello!
# HG changeset patch
# User Jiuzhou Cui
# Date 1669360043 -28800
# Fri Nov 25 15:07:23 2022 +0800
# Branch quic
# Node ID da7d9eb93afad52bd5b231501590535be9660d8c
# Parent c6580dce98a8951fcecce2daa4b6bdbda8307bf7
HTTP/3: fixed build without NGX_PCRE (broken by 0f5fc7a320db