Jetty rejects encoded URIs with HTTP/2

[npantelic]

Jetty version(s)
9.4.44.v20210927

Java version/vendor
Open JDK version 11.0.14.1

OS type/version
Both MacOS and Linux.

Description
Jetty does not accept encoded URIs over HTTP/2. It returns <h1>Bad Message 400</h1><pre>reason: Ambiguous path separator</pre>

How to reproduce?

• Use HTTP/2 connector (with ALPN; in my case with chained protocols h2, h2-17, http/1.1).
• Encode URI - / -> %2f
• Jetty returns <h1>Bad Message 400</h1><pre>reason: Ambiguous path separator</pre>

Notes:

• with HTTP/1.1 it works just fine (with default http compliance mode)
• URIs in canonical form does not make a problem
  • https://{host}:{port}/path%2Fsomething%2fsomethingelse -> works with HTTP/1.1, but not with HTTP/2
  • https://{host}:{port}/path/something/somethingelse-> works with both HTTP/1.1 and HTTP/2
• other encoded chars also make a problem

Could http compliance mode be set on http 2 connection factory or is there any workaround. Is this a known issue?

[joakime]

Seems that Issue #7710 is related

[joakime]

Or you can move to Jetty 10.0.x which has HttpCompliance and UriCompliance across all Connection Factories.

[sbordet]

Duplicate of #7710.

[npantelic]

@joakime Thanks for the answer, it helped 😄