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.

Sign up for GitHub

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

Jump to bottom

[wasm][HTTP] TypeError: Failed to fetch #53018

Closed
pavelsavara opened this issue May 20, 2021 · 4 comments · Fixed by #52923
Closed

[wasm][HTTP] TypeError: Failed to fetch #53018

pavelsavara opened this issue May 20, 2021 · 4 comments · Fixed by #52923
Labels
arch-wasm WebAssembly architecture area-System.Net.Http
Milestone
6.0.0

Comments

@pavelsavara
Copy link
Member

pavelsavara commented May 20, 2021 •
edited
Loading

Broken tests in

  • System.Net.Http.Functional.Tests.SyncHttpHandler_PostScenarioTest
  • System.Net.Http.Functional.Tests.HttpClientHandler_RemoteServerTest

Tests fail with

System.Net.Http.HttpRequestException : TypeError: Failed to fetch   at System.Net.Http.BrowserHttpHandler.SendAsync(HttpRequestMessage request, CancellationToken cancellationToken)
   at System.Net.Http.HttpClient.<SendAsync>g__Core|83_0(HttpRequestMessage request, HttpCompletionOption completionOption, CancellationTokenSource cts, Boolean disposeCts, CancellationTokenSource pendingRequestsCts, CancellationToken originalCancellationToken)
   at System.Net.Http.Functional.Tests.HttpClientHandler_RemoteServerTest.SendAsync_SendRequestUsingMethodToEchoServerWithNoContent_MethodCorrectlySent(String method, Uri serverUri)

Part of the failures could be caused by lack of CORS support on the remote test server in Azure.
@pavelsavara pavelsavara added arch-wasm WebAssembly architecture area-System.Net.Http labels May 20, 2021
@ghost
Copy link

ghost commented May 20, 2021

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

Issue Details

When running SyncHttpHandler_PostScenarioTest some of them fail with: System.Net.Http.HttpRequestException : TypeError: Failed to fetch when used with HTTP/2

Author: pavelsavara
Assignees: -
Labels:

arch-wasm, area-System.Net.Http
Milestone: -

@dotnet-issue-labeler dotnet-issue-labeler bot added the untriaged New issue has not been triaged by the area owner label May 20, 2021
@pavelsavara pavelsavara changed the title [wasm][HTTP/2] Broken System.Net.Http.Functional.Tests.SyncHttpHandler_PostScenarioTest scenarios [wasm][HTTP/2] Broken System.Net.Http.Functional.Tests.SyncHttpHandler_PostScenarioTest and System.Net.Http.Functional.Tests.HttpClientHandler_RemoteServerTest scenarios May 20, 2021
@pavelsavara pavelsavara changed the title [wasm][HTTP/2] Broken System.Net.Http.Functional.Tests.SyncHttpHandler_PostScenarioTest and System.Net.Http.Functional.Tests.HttpClientHandler_RemoteServerTest scenarios [wasm][HTTP] Broken SyncHttpHandler_PostScenarioTest and HttpClientHandler_RemoteServerTest scenarios May 20, 2021
@pavelsavara pavelsavara mentioned this issue May 20, 2021
Merged
@karelz
Copy link
Member

karelz commented May 27, 2021

@lewing @pavelsavara can you please triage this one? (set milestone + remove Untriaged label) Thanks!

@pavelsavara pavelsavara changed the title [wasm][HTTP] Broken SyncHttpHandler_PostScenarioTest and HttpClientHandler_RemoteServerTest scenarios [wasm][HTTP] TypeError: Failed to fetch Jun 2, 2021
pavelsavara added a commit to pavelsavara/runtime that referenced this issue Jun 2, 2021
@pavelsavara
- disabled tests with dotnet#53018
951f5b9 
- disabled tests with dotnet#53591
- disabled tests with dotnet#53592
pavelsavara added a commit that referenced this issue Jun 2, 2021
@pavelsavara
[wasm] Enable more networking tests (#53027)
1e19518 
- enable System.Net.Http.Functional.Tests on browser
- System.Net.Http.Functional.Tests to run in chrome instead of V8 via WasmTestOnBrowser
- ActiveIssue #34690 for WebSocket on Windows Mono
- fix Quic detection in test
- disable webSocket tests on Mono/Windows
- disable tests with MaxConnectionsPerServer not supported on Browser
- disable tests with Socket not supported on Browser
- disable tests with AutomaticDecompression not supported on Browser
- disable tests with UseProxy not supported on Browser
- disable tests with PreAuthenticate not supported on Browser
- disable tests with Credentials is not supported on Browser
- disable tests with Loopback server
- run outerloop on browser, rather than V8 only
- [ActiveIssue] #37669 for missing crypto MD5
- conditional tests with PlatformDetection.IsBrowserDomSupportedOrNotBrowser to allow System.Net.Http.Functional.Tests pass on V8
- disabled tests with #53018
- disabled tests with #53591
- disabled tests with #53592
@pavelsavara pavelsavara mentioned this issue Jun 3, 2021
Merged
@ghost ghost added the in-pr There is an active PR which will close this issue when it is merged label Jun 3, 2021
@pavelsavara
Copy link
Member Author

Caused by using HTTPS for HTTP listener port in the unit test.

@karelz karelz added this to the 6.0.0 milestone Jun 8, 2021
@karelz karelz removed the untriaged New issue has not been triaged by the area owner label Jun 8, 2021
@karelz
Copy link
Member

karelz commented Jun 8, 2021

@pavelsavara FYI: I marked it triaged on your behalf

@ghost ghost removed the in-pr There is an active PR which will close this issue when it is merged label Jun 9, 2021
@ghost ghost locked as resolved and limited conversation to collaborators Jul 9, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
arch-wasm WebAssembly architecture area-System.Net.Http
Projects
None yet
Milestone
6.0.0
Development

Successfully merging a pull request may close this issue.

[wasm][testing] hosting echo server in xharness process pavelsavara/runtime
2 participants
@pavelsavara @karelz