Search code examples
httpurlweburihttp2

HTTP/2 -- what's going on?


I plan to code a mighty web server. But I am unsure: should I do it in HTTP/1.x, or HTTP/2? I really don't like doing it in both (I know HTTP/2 is backward compatible to HTTP/1.x, but if it's superior AND is going to be adopted by the majority then I will only do it in HTTP/2 without the backward compatibility aspect).

How is the future looking like for HTTP/2? Are there any hints from standard bodies to change HTTP/2 or undo their mistakes?

Is HTTP/2 really worth it?

Finally, how is the expected HTTP/2 adoption by web browsers?


Solution

  • How is the future looking like for HTTP/2? and Finally, how is the expected HTTP/2 adoption by web browsers?

    The HTTP/2 standard has passed acceptance and is being implemented by all major server vendors. In fact, server support has advanced, all major server vendors support HTTP/2 in their current releases. You can track all known implementations of HTTP/2 here.

    Are there any hints from standard bodies to change HTTP/2 or undo their mistakes?

    There will not be an HTTP 2.x. The standards body has already made this clear (although I can't find a link that proves it). the next version will be HTTP/3.

    Is HTTP/2 really worth it? Yes. The benefits of HTTP/2 are too long to list here. This article discusses them in depth.

    When developing a web server you will need to take account of both HTTP1.x and HTTP/2. At the moment we are transitioning to HTTP/2 but you should provide backward compatibility to HTTP/1.x.