Why bundle optimizations are no longer a concern in HTTP/2

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

Optimizing File Cacheing and HTTP2

Let’s clarify a few things: My understanding is that http2 renders optimization techniques like file concatenation obsolete, since a server using http2 just sends one request. HTTP/2 renders optimisation techniques like file concatenation somewhat obsolete since HTTP/2 allows many files to download in parallel across the same connection. Previously, in HTTP/1.1, the browser could request … Read more

Is the per-host connection limit raised with HTTP/2?

Browsers impose a per-domain limit of 6-8 connections when using HTTP/1.1, depending on the browser implementation. This allows at most 6-8 concurrent requests per domain. With HTTP/2, browsers open only 1 connection per domain. However, thanks to the multiplexing feature of the HTTP/2 protocol, the number of concurrent requests per domain is not limited to … Read more

How to make the .net HttpClient use http 2.0?

1.Make sure you are on the latest version of Windows 10. 2.Install WinHttpHandler: Install-Package System.Net.Http.WinHttpHandler 3.Extend WinHttpHandler to add http2.0 support: public class Http2CustomHandler : WinHttpHandler { protected override Task<HttpResponseMessage> SendAsync(HttpRequestMessage request, System.Threading.CancellationToken cancellationToken) { request.Version = new Version(“2.0”); return base.SendAsync(request, cancellationToken); } } 4.Pass above handler to the HttpClient constructor using (var httpClient = … Read more