-
Notifications
You must be signed in to change notification settings - Fork 5.2k
[browser][http] mute JS exceptions about network errors + HEAD verb #113014
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Tagging subscribers to this area: @dotnet/ncl |
Co-authored-by: campersau <[email protected]>
…ara/runtime into browser_http_mute_abort
src/libraries/Common/tests/System/Net/Prerequisites/NetCoreServer/Handlers/EchoHandler.cs
Outdated
Show resolved
Hide resolved
…ver/Handlers/EchoHandler.cs Co-authored-by: Alexander Köplinger <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some nits
src/libraries/Common/tests/System/Net/Http/ResponseStreamTest.cs
Outdated
Show resolved
Hide resolved
src/libraries/Common/tests/System/Net/Http/ResponseStreamTest.cs
Outdated
Show resolved
Hide resolved
src/libraries/Common/tests/System/Net/Prerequisites/NetCoreServer/Handlers/EchoHandler.cs
Outdated
Show resolved
Hide resolved
Co-authored-by: campersau <[email protected]>
…ver/Handlers/EchoHandler.cs Co-authored-by: campersau <[email protected]>
Co-authored-by: campersau <[email protected]>
/ba-g known CI issue #110805 |
/backport to release/9.0 |
Started backporting to release/9.0: https://github.com/dotnet/runtime/actions/runs/13725376350 |
In browser HTTP client we subscribe for rejected promises in order to suppress unhandled rejection of
AbortError
when we issue the abort. The current handler also handles other network errors and aborts the whole program, which is not what it should do. Instead the network error should be propagated to managed HTTP client code.in Firefox when the verb is HEAD, the body is null. We should not fail because of that.
Passing
Response
as result ofhttp_wasm_fetch
is creating JS memory leak by marshaling the object.Contributes to #112172
Contributes to #111992
This bug fix should be back ported.