Add experimental HTTP/3 via Quiche #433
Draft
Conversation
This file contains hidden or 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
Expose the ability to compile in HTTP/3 support via Quiche. Curl is currently experimenting with multiple QUIC backends right now so the feature name specifies Quiche explicitly. This requires a fork of Quiche at the moment to expose the C header path as Cargo build metadata. I will look into whether this is something the Quiche developers would add upstream, though it is a bit more complicated than with Rustls since the C API is part of the same crate and may not want to use the `links` Cargo option.
This was referenced Nov 22, 2022
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.
Expose the ability to compile in HTTP/3 support via Quiche. Curl is currently experimenting with multiple QUIC backends right now so the feature name specifies Quiche explicitly.
This requires a fork of Quiche at the moment to expose the C header path as Cargo build metadata. I will look into whether this is something the Quiche developers would add upstream, though it is a bit more complicated than with Rustls since the C API is part of the same crate and may not want to use the
linksCargo option.