implement the HTTP/3 Datagram negotiation #2951
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
marten-seemann
force-pushed
the
h3-datagram-negotiation
branch
from
e6cb11b
to
d510eea
Compare
Codecov Report
@@ Coverage Diff @@
## master #2951 +/- ##
==========================================
+ Coverage 86.12% 86.18% +0.06%
==========================================
Files 134 134
Lines 9326 9364 +38
==========================================
+ Hits 8032 8070 +38
Misses 935 935
Partials 359 359
Continue to review full report at Codecov.
|
lucas-clemente
approved these changes
Dec 22, 2020
marten-seemann
force-pushed
the
h3-datagram-negotiation
branch
from
d510eea
to
b753005
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Depends on #2949.
According to https://www.ietf.org/archive/id/draft-schinazi-masque-h3-datagram-02.html.
This PR only adds support for writing and parsing of the datagram option in the HTTP/3 SETTINGS frame, as well as adds the check that datagram support was enabled on the QUIC layer if both client and server negotiated it on the H3 layer.
It is not yet possible to actually send and receive H3 datagrams. That will be added in a subsequent PR.