RFR: 8349910: Implement HTTP/3 for the HTTP Client API

[Michael McMahon]

On Fri, 18 Apr 2025 18:47:52 GMT, Chen Liang <liach at openjdk.org> wrote:

>> Hi,
>> 
>> Please find here a PR for the implementation of JEP [JDK-8291976: HTTP/3 for the HTTP Client API](https://bugs.openjdk.org/browse/JDK-8291976).
>> 
>> The CSR can be viewed at [JDK-8350588: Implement HTTP/3 for the HTTP Client API](https://bugs.openjdk.org/browse/JDK-8350588)
>> 
>> This JEP proposes to enhance the HttpClient implementation to support HTTP/3.
>> It adds a non-exposed / non-exported internal implementation of the QUIC protocol based on DatagramChannel and the SunJSSE SSLContext provider.
>
> src/java.net.http/share/classes/java/net/http/HttpResponse.java line 838:
> 
>> 836:         /**
>> 837:          * Represents a HTTP/3 PushID. PushIds can be shared across
>> 838:          * multiple client initiated requests on the same HTTP/3 connection.
> 
> Is this a marker interface for various kinds of push ids? Otherwise just the record is sufficient.

We had to change the API going from HTTP/2 push promise to HTTP/3. So, we want to avoid having to do that again (except where necessary) in any future update to the definition of a Push ID. I think Push Promise is a fairly esoteric aspect of HTTP anyway and won't concern the majority of developers.

-------------

PR Review Comment: https://git.openjdk.org/jdk/pull/24751#discussion_r2055781501