-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
[browser][http] mute JS exceptions about network errors + HEAD verb #113014
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Tagging subscribers to this area: @dotnet/ncl |
campersau
reviewed
Feb 28, 2025
Co-authored-by: campersau <buchholz.bastian@googlemail.com>
…ara/runtime into browser_http_mute_abort
This was referenced Feb 28, 2025
3 tasks
This was referenced Mar 3, 2025
…ara/runtime into browser_http_mute_abort
campersau
reviewed
Mar 6, 2025
akoeplinger
approved these changes
Mar 7, 2025
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 <alex.koeplinger@outlook.com>
javiercn
approved these changes
Mar 7, 2025
campersau
approved these changes
Mar 7, 2025
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 <buchholz.bastian@googlemail.com>
…ver/Handlers/EchoHandler.cs Co-authored-by: campersau <buchholz.bastian@googlemail.com>
Co-authored-by: campersau <buchholz.bastian@googlemail.com>
/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 |
4 tasks
pavelsavara
added a commit
to pavelsavara/runtime
that referenced
this pull request
Mar 7, 2025
4 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.