Support HTTP/3 in Jetty and JRE HTTP Client#1949
Draft
kwin wants to merge 7 commits into
Draft
Conversation
kwin
force-pushed
the
feature/http3
branch
2 times, most recently
from
95b0e32 to
0dd1244
Compare
Consolidate http version configuration among HTTP transporters Default to HTTP/2 in all transporters except Apache HTTP Client 4.x Still WIP
Member
Author
|
@vy Maybe you can have a look. Connecting from Java HTTP Client via HTTP3 to a local Jetty HTTP/3 server fails in Logging enabled with The same endpoint works fine with Jetty HTTP/3 client. |
kwin
force-pushed
the
feature/http3
branch
2 times, most recently
from
c2376c1 to
612993d
Compare
Member
|
feature-http3-jdk-fix.patch — contributed by @dfuch and @jaikiran — fixes
|
Member
Author
|
@vy Thanks a lot. I raised jetty/jetty.project#15385 because the Quiche binding missing currently is just silently discarded in Jetty. I meanwhile figured out how to properly connect with JRE HTTP Client to Jetty via HTTP/3. However I am still missing an insecure option (to completely skip the server's certificate check) |
Clean up and regenerate key stores Cleanup server method names
kwin
force-pushed
the
feature/http3
branch
2 times, most recently
from
cf7c79d to
8aa84dd
Compare
kwin
force-pushed
the
feature/http3
branch
2 times, most recently
from
8daa9e2 to
59de191
Compare
Member
Author
|
@cstamas I don't understand the unstable test |
kwin
commented
Jul 9, 2026
| * | ||
| * @configurationSource {@link RepositorySystemSession#getConfigProperties()} | ||
| * @configurationType {@link ConfigurationProperties.HttpVersion} | ||
| * @configurationDefaultValue {@link #DEFAULT_HTTP_VERSION} |
Member
Author
There was a problem hiding this comment.
@cstamas This constant cannot be extracted with
. Any idea how to fix this?
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Consolidate http version configuration among HTTP transporters Default to HTTP/2 in all transporters except Apache HTTP Client 4.x
Still WIP
Following this checklist to help us incorporate your
contribution quickly and easily:
Note that commits might be squashed by a maintainer on merge.
This may not always be possible but is a best-practice.
mvn verifyto make sure basic checks pass.A more thorough check will be performed on your pull request automatically.
mvn -Prun-its verify).If your pull request is about ~20 lines of code you don't need to sign an
Individual Contributor License Agreement if you are unsure
please ask on the developers list.
To make clear that you license your contribution under
the Apache License Version 2.0, January 2004
you have to acknowledge this by using the following check-box.