At the time of writing three server vendors currently support Servlet 4.0, Apache Tomcat 9.0.0.M4, Jetty 9 and WildFly 10.0.0.Final. Let’s have a look at how to configure Tomcat 9 to support. The Goal of HTTP/2 The goal of HTTP/2 is to increase the perceived performance of the web browsing experience. By default Tomcat will ignore all trailer headers when processing HTTP/2 connections. For a header to be processed, it must be added to this comma-separated list of header names. InitialWindowSize: Controls the initial size of the flow control window for streams that Tomcat advertises to clients. 是自1999年http1.1发布后的首个更新。系统环境：CentOS release 6.5 (Final) x64JDK 1.8.092apache-tomcat-9.
Brew update mtr. I tried configuring SSL in Tomcat 9 using Http11NioProtocol and the Apache Axis service worked fine on port 8443. So the Http11AprProtocol or Http2Protocol is the one causing the problem. Java openssl axis http2 tomcat9. Tomcat server version 9+ enables support for the h2 protocol (the modjk Apache module can be directly used to connect with Tomcat over h2, but I used modproxyhttp2 to show the general scenario).
From version 9 onwards, Tomcat has support for HTTP/2 but not the default. Wanting to work with HTTP/2 with Tomcat, we must have some adjustments in its configuration. In this tutorial, I will guide you.
First of all, you have to make sure that you are using Java 9 or above.
Because of only Java 9 and above supporting for Application-Layer Protocol Negotiation (ALPN). ALPN is a Transport Layer Security extension, which allows Tomcat to choose the version of the HTTP protocol that it will work with.
Currently, I have installed Java 9:
The second step we need to do is modify the server.xml file located in the conf directory of Tomcat.
The definition of HTTP/2 is not required to use a secure connection, but browsers implement it with a secure connection, so we will configure HTTP/2 support for Tomcat with HTTPS protocol.
In the previous tutorial, I have shown you how to configure HTTPS for Tomcat, the content of the Tomcat Connector for HTTPS is as follows:
Tomcat 9 Http2
Now, for HTTP/2 support, we will add a child tag named UpgradeProtocol inside the Connector tag with the following content:
That’s all we need.
Tomcat 9 Http2 Without Ssl
To check the results, just visit https://localhost:8443/. If you are using Chrome, right click on the site, select Inspect, then select the Network tab. Refresh the site, you will see the results as follows:
Tomcat 9 Enable Http2
Note the localhost line in the picture, you will see the protocol is h2, which means HTTP/2.