Uh oh!
There was an error while loading. Please reload this page.
[HTTP/3] Fix handling cancelation during QUIC connection establishment - #87971
Conversation
ghost
commented
Jun 23, 2023
Tagging subscribers to this area: @dotnet/ncl Issue DetailsWhen a new Discovered in stress test as they randomly cancel requests. Fixes #87957
|
ManickaP
commented
Jun 23, 2023
/azp run runtime-libraries stress-http |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
ManickaP
commented
Jun 26, 2023
/azp run runtime-libraries stress-http |
|
Azure Pipelines successfully started running 1 pipeline(s). |
ManickaP
commented
Jun 26, 2023
/azp run runtime-libraries stress-http |
|
Azure Pipelines successfully started running 1 pipeline(s). |
ManickaP
commented
Jun 26, 2023
Stress is green. |
When a new
QuicConnectionis being established for HTTP/3 and it fails, we block the remote authority and remember why. Any further attempt to connect to that authority gets failed with that reason for a while.We shouldn't do that if the failure is because we decided to stop the attempt, i.e. we (timeout) or user cancelled the passed in token.
Discovered in stress test as they randomly cancel requests.
Fixes#87957