Set a default for the Http3Support feature switch #10251
Conversation
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
MichalStrehovsky
requested review from
jonathanpeppers and
grendello
as code owners
|
Since it's a potentially breaking change (it removes something by default where it was present before and moves the responsibility for this to app developers), can you add documentation for this new default and how to enable HTTP3 support? I think the best place would be somewhere in this file, since the content of the @jonathanpeppers do you agree we should document this in the above location? |
|
I don't think this ever worked on Android. It needs msquick library which AFAIK we never shipped for Android. |
If this is so, then there wouldn't be any need to document this, indeed. Not unless we plan to start supporting it on Android at some point? |
No, we don't officially support QUIC on Android, as a result we don't support HTTP/3 on Android. However, it might be possible for users to compile msquic themselves and use it. cc @ManickaP |
Yep and before this feature switch got introduced in dotnet/runtime#117012, not even building your own libmsquic would be enough because it was force disabled in System.Net.Http. With this feature switch the user will have an option to flip the switch and experiment if they really want. Android behavior was discussed at dotnet/runtime#117012 (comment). |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
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