Skip to content
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

[release/9.0] [browser][http] mute JS exceptions about network errors + HEAD verb #113261

Open
wants to merge 14 commits into
base: release/9.0-staging
Choose a base branch
from

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Mar 7, 2025

Backport of #113014 to release/9.0

/cc @pavelsavara

Customer Impact

  1. 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.

  2. in Firefox when the verb is HEAD, the body is null. We should not fail because of that.

  3. Passing Response as result of http_wasm_fetch is creating JS memory leak by marshaling the object.

  • Customer reported
  • Found internally

Fixes #112172
Contributes to #111992

Regression

  • Yes
  • No

Testing

Automated tests.

Risk

Low

Both issues are only triggered when user enabled streaming responses. That's opt-in feature in Net9 and below.

pavelsavara and others added 13 commits March 7, 2025 16:54
Co-authored-by: campersau <buchholz.bastian@googlemail.com>
…ver/Handlers/EchoHandler.cs

Co-authored-by: Alexander Köplinger <alex.koeplinger@outlook.com>
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>
@dotnet-issue-labeler dotnet-issue-labeler bot added the needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners label Mar 7, 2025
@pavelsavara pavelsavara self-assigned this Mar 7, 2025
@pavelsavara pavelsavara added arch-wasm WebAssembly architecture area-System.Net.Http os-browser Browser variant of arch-wasm and removed needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners labels Mar 7, 2025
@pavelsavara pavelsavara added this to the 9.0.x milestone Mar 7, 2025
Copy link
Contributor

Tagging subscribers to this area: @dotnet/ncl
See info in area-owners.md if you want to be subscribed.

@pavelsavara pavelsavara requested review from akoeplinger and maraf March 7, 2025 17:03
@pavelsavara
Copy link
Member

cc @campersau

@lewing lewing added the Servicing-consider Issue for next servicing release review label Mar 7, 2025
@pavelsavara pavelsavara changed the base branch from release/9.0 to release/9.0-staging March 7, 2025 17:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
arch-wasm WebAssembly architecture area-System.Net.Http os-browser Browser variant of arch-wasm Servicing-consider Issue for next servicing release review
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants