> On 2025 Feb 11, at 19:21, Amit Pande <amit.pa...@veritas.com.invalid> wrote: > > Am planning to update the Tomcat configuration to support HTTP/2. > > Wanted to understand the difference between > > <UpgradeProtocol className="org.apache.coyote.http2.Http2Protocol"/> nested > within the HTTP/1.1 connector > > Vs > > Supporting protocol=org.apache.coyote.http2.Http2Protocol in the connector > configuration.
I don’t see anywhere in the documentation for supported Tomcat levels where the “protocol=…Http2Protocol” setting is allowed. Where did you come up with that? > As I understand using the upgrade protocol mechanism allows to fallback on > HTTP 1.1 in case the client and server don't agree on HTTP2. Is this right > understanding? Yes - hence the <UpgradeProtocol> element within the <Connector> element rather than an additional protocol attribute. > Were there any other design considerations to support HTTP/2 via upgrade > protocol mechanisms? My apologies but I didn't find details around this. That question is a bit vague… - Chuck --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
