“Everything was easier back then” – it’s a sentiment we all hear from time to time. When it comes to websites, this is perfectly true. After all, websites in the 1990s were downright spartan in their approach to web design. And there was little emphasis on aesthetics, what with the prevalence of flashing GIFs. This era also saw the advent of the HTTP protocol, which controls how web servers and web browsers communicate with one another. But while technology and website programming developed swiftly, the HTTP protocol only actually received a minor update once back in 1999 – so it’s no wonder that HTTP/1.1 feels a little out of date.
With the launch of the much more powerful HTTP/2, our customers can now benefit from the latest version of the HTTP protocol on all of our servers. Just take a look at your own website to see the difference.
Is HTTP/2 now ready for operation?
Thanks to the recently completed web server update to Apache 2.4, HTTP/2 is now available for all websites hosted by Hostpoint. However, as the majority of browsers do not support HTTP/2 for unencrypted connections, unencrypted HTTP requests will continue to be made via HTTP/1.1 and will therefore not be able to benefit from the new features.
If your website does not yet have an SSL certificate, it is probably now time to activate SSL. You can do so in just a few clicks – our own FreeSSL, which is free of charge, is an ideal option.
And what about browsers used by website visitors? With the exception of Opera Mini, all current browser versions should support HTTP/2. An overview of browser compatibility is available at Can i use.
How will HTTP/2 change things for web developers?
For web developers, HTTP/2 means a departure from tried and tested procedures. In future, you will no longer have to rely on unappealing workarounds such as domain sharding, concatenation and sprites or resource inlining, as these techniques will, for the most part, become obsolete thanks to the innovations offered by HTTP/2. Developers can find more interesting information about HTTP/2 on IETF’s HTTP/2 page or at http2 explained by Daniel Stenberg.