Thanks for the mention, Saurabh! I’m curious how people make HTTP2 available for us. How do we know if we’re already making some HTTP2/3 requests? Will this be an implementation detail on the client level (curl or a web browser) that we don’t have to care about?
Very useful article. Just one doubt about the image inside Point 5. In the second request, are headers already sent in the previous request really left out or are they replaced with an index from the dynamic table?
Thanks for the mention, Saurabh! I’m curious how people make HTTP2 available for us. How do we know if we’re already making some HTTP2/3 requests? Will this be an implementation detail on the client level (curl or a web browser) that we don’t have to care about?
Most browsers already support HTTP 2 and 3 as well. So the client part from a browser perspective is pretty much taken care of.
Now it's mostly up to the application teams to configure their web servers to support HTTP 2 or 3 depending on how soon they want to upgrade.
Thanks for the clarification Saurabh! 🫡
it is very clear and informative , thank Saurabh
Thanks for the feedback!
Very useful article. Just one doubt about the image inside Point 5. In the second request, are headers already sent in the previous request really left out or are they replaced with an index from the dynamic table?