Skip to content

Conversation

MihaZupan
Copy link
Member

Closes #117942

I added the test just to see if large Uris flow through the SocketsHttpHandler stack E2E, not that interesting for browser.

@MihaZupan MihaZupan added this to the 10.0.0 milestone Jul 22, 2025
@Copilot Copilot AI review requested due to automatic review settings July 22, 2025 19:58
Copy link
Contributor

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR disables the LargeUriAndHeaders_Works test on browser platforms by changing it from a [Fact] to a [ConditionalFact] that only runs when not on browser. The test was originally designed to validate large URI handling through the SocketsHttpHandler stack end-to-end, which is not relevant for browser environments.

Key changes:

  • Changed test attribute from [Fact] to [ConditionalFact] with browser exclusion
  • Removed browser-specific length logic since the test no longer runs on browser

Copy link
Contributor

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

@MihaZupan
Copy link
Member Author

/ba-g Build analysis isn't picking up WASM queue timeouts

@MihaZupan MihaZupan merged commit de4440c into dotnet:main Jul 23, 2025
81 of 87 checks passed
@github-actions github-actions bot locked and limited conversation to collaborators Aug 23, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Timeout in WASM run for System.Net.Http.Functional.Tests.SocketsHttpHandler_HttpClientHandlerTest.LargeUriAndHeaders_Works

2 participants