RFR: 8354276: Strict HTTP header validation [v4]

[Daniel Fuchs]

On Thu, 10 Apr 2025 16:35:01 GMT, Daniel Jeliński <djelinski at openjdk.org> wrote:

>> RFC 9113 HTTP/2 mandates certain validation for HTTP headers; the HttpClient don't fully implement the described requirements.
>> 
>> This PR adds the following validation:
>> - pseudo-headers defined for requests are rejected in responses and push streams
>> - pseudo-headers defined for responses are rejected in push promises
>> - connection headers are rejected in responses and push streams
>> 
>> Connection headers are still accepted in push promises; that's because some popular server implementations were found to echo the request headers in push promises, and when the original request was a HTTP/1 upgrade, the push promise could contain one or more headers that were prohibited in HTTP/2 but allowed in HTTP/1.
>> 
>> An existing test was adapted to verify the handling of response headers. The modified test passes with this the changes in this PR, fails without them. Other tier1-3 tests continue to pass.
>
> Daniel Jeliński has updated the pull request incrementally with two additional commits since the last revision:
> 
>  - Fix whitespace
>  - Use ProtocolException for malformed headers

src/java.net.http/share/classes/jdk/internal/net/http/Http2Connection.java line 988:

> 986:                     // connection-level HPACK decoding state
> 987:                     if (orphanedConsumer == null || frame.getClass() != ContinuationFrame.class) {
> 988:                         orphanedConsumer = new ValidatingHeadersConsumer(Context.RESPONSE);

Should the context be `Context.REQUEST` if `hf instanceof PushPromiseFrame`?

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

PR Review Comment: https://git.openjdk.org/jdk/pull/24569#discussion_r2063733675