Uh oh!
There was an error while loading. Please reload this page.
[HTTP/3] Stress disable offending op causing server errors - #58442
Conversation
ghost
commented
Aug 31, 2021
Tagging subscribers to this area: @dotnet/ncl Issue DetailsKestrel doesn't like Expect 100 Continue in H/3. See #58110 (comment)
|
ManickaP
commented
Aug 31, 2021
/azp run runtime-libraries stress-http |
|
Azure Pipelines successfully started running 1 pipeline(s). |
karelz
commented
Aug 31, 2021
@ManickaP this may be worth backporting to 6.0, right? |
ManickaP
commented
Sep 1, 2021
Yep, @antonfirsov did some PRs enabling the stress pipeline there (has it been merged?), so we should probably get this there as well. |
ManickaP
commented
Sep 2, 2021
/backport to release/6.0 |
Started backporting to release/6.0: https://github.com/dotnet/runtime/actions/runs/1193516392 |
adityamandaleeka
commented
Sep 10, 2021
@ManickaP FYI, we are about to get 100 continue support for h3 into Kestrel in both main and 6.0 dotnet/aspnetcore#36168 (main) Thanks again for finding this! |
ManickaP
commented
Sep 13, 2021
Awesome, thanks! I'll update the stress tests once it gets into the nightly docker image. |
Kestrel doesn't like Expect 100 Continue in H/3.
See #58110 (comment)
Contributes to #56310
Fixes#55261