HTTP / 1.1 or HTTPS / 2?
The new HTTPS / 2 protocol promises a better and especially smarter connection via the internet so that websites can load faster up to 3% to 15% faster.
At all website and server connections run over HTTP / 2 as standard
What is HTTP / 2?
HTTP / 2 is a renewed transfer protocol released in 2017.
Actually it is a major upgrade of the old HTTP / 1.1 protocol that already became the standard for all HTTP connections over the internet in 1997.
But since 1997 the web has also become many times larger with much more complex data and multi-media content. The old HTTP / 1.1 protocol can process this growth in data less and less efficiently, so the HTTP / 2 protocol was released in 2017 based on the SPDY developed by Google as: Speedy.
How does HTTP / 2 work?
When you make contact with a website, your internet browser will start an HTTP connection with the server. If they both support HTTPS / 2, the server will use the HTTP / 2 protocol and let the connection run over the HTTP / 2 network. If either of them does not support the HTTP / 2 protocol, the browser and / or server will fall back on the old HTTP / 1.1 protocol.
HTTP / 2 is a lot safer.
HTTP / 2 responds to the need of website visitors for security and therefore the use of an SSL certificate is the standard standard for HTTP / 2.
Http / 2 improves the old HTTP / 1.1 on the following points.
Multiplexing: With 1.1, the protocol can only retrieve the files one by one per connection. This means: requesting a file, waiting for a response, downloading the file and then asking for the following. For pages with a high number of requests, this greatly reduces loading. In addition, current websites request content from multiple sources (advertising networks, optimization scripts, content delivery networks, etc.). With HTTP / 1.1 this opens many different TCP connections.
Header optimization: Every HTTP request contains header information. With HTTP / 1.1, many of those headers were repeated during a session. With HTTP / 2, unnecessary headers are removed and the remaining headers are compressed.
Server Push: With HTTP / 1.1, the server had to wait until the client initiated a connection. With HTTP / 2, servers can immediately push resources proactively to the client. Specifically: when your browser contacts a web server and requests a web page, the HTML file is sent first. Then your browser asks for the JavaScript files, images, CSS, etc. - that of course means a multitude of connections that go back and forth and delay the display of the page. With HTTP / 2 the server will know what content your browser needs to render the page. He will push this data to your browser before it asks for it.
If you really want to know everything about HTTP / 1.1 and HTTP / 2
Then check the wikipedia website

Thursday, April 4, 2019

« Back