Take stackoverflow for example, when the browser sends a request to stackoverflow.com, it has to do the following steps: DNS lookup. find the ip address of stackoverflow. TCP/IP handshake TLS handshake. HTTP request/response (Application Protocol). …. TLS handshake Regarding step3 TLS handshake, there is an nice explanation by @Oleg. In order to inspect the detail … Read more
The bundling optimization was introduced as a “best practice” when using HTTP/1.1 because browsers could only open a limited number of connections to a particular domain. A typical web page has 30+ resources to download in order to be rendered. With HTTP/1.1, a browser opens 6 connections to the server, request 6 resources in parallel, … Read more
HTTP/2 supported: $ curl -sI https://curl.se -o/dev/null -w ‘%{http_version}\n’ 2 HTTP/2 not supported (instead serving 1.1 in this case): $ curl -sI http://curl.se -o/dev/null -w ‘%{http_version}\n’ 1.1 (curl 7.50.0 or later is required for this command line to work) HTTP/3 Since curl 7.88.1, if you build curl to support HTTP/3, the above one-liner can be … Read more
HTTP/1.1 without pipelining: Each HTTP request over the TCP connection must be responded to before the next request can be made. HTTP/1.1 with pipelining: Each HTTP request over the TCP connection may be made immediately without waiting for the previous request’s response to return. The responses will come back in the same order. HTTP/2 multiplexing: … Read more
Technically There are several technical reasons why HTTP/2 is much better and easier to handle over HTTPS: Doing HTTP/2 negotiation in TLS with ALPN is much easier and doesn’t lose round-trips like Upgrade: in plain HTTP does. And it doesn’t suffer from the upgrade problem on POST that you get with plain-text HTTP/2. N% of … Read more
I’m the HTTP/2 implementer in Jetty, and I watch out other projects implementing HTTP/2. Tomcat’s Mark Thomas has outlined support for HTTP/2 for Tomcat 9. Update Jan 2017: Tomcat 8.5 supports HTTP/2 see @joe-aldrich answer https://stackoverflow.com/a/37889873/2027465 Considering that Servlet 4.0 is going to have as a target HTTP/2 support, and that HTTP/2 support requires ALPN … Read more
They’re still useful. HTTP/2 reduces the impact of some of these practices, but it doesn’t eliminate their impact. Minification remains as useful as ever. Although HTTP/2 introduces new compression for message headers, that has nothing to do with minification (which is about message bodies). The compression algorithms for message bodies are the same, so minification … Read more
HTTP Head of line blocking Head of Line blocking in HTTP terms is often referring to the fact that each browser/client has a limited number of connections to a server and doing a new request over one of those connections has to wait for the ones to complete before it can fire it off. The … Read more
In Spring Boot 2.1 and above it is as simple as adding this property to your .properties (or .yml) file: server.http2.enabled=true You can also do it programmatically like this (in one of your configuration classes): @Bean public ConfigurableServletWebServerFactory tomcatCustomizer() { TomcatServletWebServerFactory factory = new TomcatServletWebServerFactory(); factory.addConnectorCustomizers(connector -> connector.addUpgradeProtocol(new Http2Protocol())); return factory; }
The main semantic of HTTP has been retained in HTTP/2. This means that it still has HTTP methods such as GET, POST, etc., HTTP headers, and URIs to identify resources. What has changed in HTTP/2 with respect to HTTP/1.1 is the way the HTTP semantic (e.g. “I want to PUT resource /foo on host example.com“) … Read more