Skip to content

Set a default for the Http3Support feature switch#23221

Closed
MichalStrehovsky wants to merge 1 commit intodotnet:mainfrom
MichalStrehovsky:patch-1
Closed

Set a default for the Http3Support feature switch#23221
MichalStrehovsky wants to merge 1 commit intodotnet:mainfrom
MichalStrehovsky:patch-1

Conversation

@MichalStrehovsky
Copy link
Member

Control over this is moving from dotnet/runtime repo build time to publish time so we need to set a default that matches the old build-time setting.

Ref dotnet/runtime#117012
Ref dotnet/sdk#49564

Control over this is moving from dotnet/runtime repo build time to publish time so we need to set a default that matches the old build-time setting.

Ref dotnet/runtime#117012
Ref dotnet/sdk#49564
@rolfbjarne
Copy link
Member

@MichalStrehovsky did http3 ever work on Apple platforms?

@rolfbjarne
Copy link
Member

Closing in favor of #23223, because our CI can't work with pull requests from forks.

@rolfbjarne rolfbjarne closed this Jun 27, 2025
@MichalStrehovsky
Copy link
Member Author

@MichalStrehovsky did http3 ever work on Apple platforms?

It didn't. There was hardcoded logic in System.Net.Http that allowed this code to also be trimmed away. I'm making this a feature switch instead of a hardcoded check, so we need to set a default for the feature switch to keep the trimming behavior.

@MichalStrehovsky MichalStrehovsky deleted the patch-1 branch June 27, 2025 10:41
rolfbjarne added a commit that referenced this pull request Jul 3, 2025
Control over this is moving from dotnet/runtime repo build time to publish time so we need to set a default that matches the old build-time setting.

Ref dotnet/runtime#117012
Ref dotnet/sdk#49564

This is a re-creation of #23221 using origin, since we can't build PRs from forks.

---------

Co-authored-by: Michal Strehovský <MichalStrehovsky@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants