-
Notifications
You must be signed in to change notification settings - Fork 25k
[RC1] Doc Http/3 for Http.Sys #23252
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
Conversation
|
What about: |
That's only required for HttpClient. |
|
@Rick-Anderson the monikers need work. How should we handle them for 5.0 and 3.1? |
Rick-Anderson
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Rick-Anderson the monikers need work. How should we handle them for 5.0 and 3.1?
I can fork this and fix them. You can review my PR and merge into this branch. OR, I could just create a new PR with them fixed and all the content you have here. Your call.
|
|
||
| ## HTTP/3 support | ||
|
|
||
| [HTTP/3](https://quicwg.org/base-drafts/draft-ietf-quic-http.html) is enabled for ASP.NET Core apps if the following base requirements are met: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| [HTTP/3](https://quicwg.org/base-drafts/draft-ietf-quic-http.html) is enabled for ASP.NET Core apps if the following base requirements are met: | |
| [HTTP/3](https://quicwg.org/base-drafts/draft-ietf-quic-http.html) is enabled for ASP.NET Core apps when the following base requirements are met: |
I should probably make a RC1 branch and when this is finished, merge to RC1. At RC1, we can merge the RC1 branch into main. |
Whatever's easier for you. |
|
@Tratcher I can always prepare the |
|
moved to #23257 |
Fixes dotnet/aspnetcore#35204
Consider holding this update until RC1 releases.