Embedded Files
Why to revise HTTP/1.1?
Why to revise HTTP/1.1?
The Hypertext Transfer Protocol (HTTP) is a wildly successful protocol. However, the way HTTP/1.1 uses the underlying transport ([RFC7230], Section 6) has several characteristics that have a negative overall effect on application performance today.
In particular, HTTP/1.0 allowed only one request to be outstanding at a time on a given TCP connection. HTTP/1.1 added request pipelining, but this only partially addressed request concurrency and still suffers from head-of-line blocking. Therefore, HTTP/1.0 and HTTP/1.1 clients that need to make many requests use multiple connections to a server in order to achieve concurrency and thereby reduce latency.
Furthermore, HTTP header fields are often repetitive and verbose, causing unnecessary network traffic as well as causing the initial TCP [TCP] congestion window to quickly fill. This can result in excessive latency when multiple requests are made on a new TCP connection.
HTTP 2.0 addresses above issues
How HTTP/2 addresses above issues?
How HTTP/2 addresses above issues?
HTTP/2 addresses these issues by defining an optimized mapping of HTTP's semantics to an underlying connection. Specifically, it allows interleaving of request and response messages on the same connection and uses an efficient coding for HTTP header fields. It also allows prioritization of requests, letting more important requests complete more quickly, further improving performance.
The resulting protocol is more friendly to the network because fewer TCP connections can be used in comparison to HTTP/1.x. This means less competition with other flows and longer-lived connections, which in turn lead to better utilization of available network capacity. Finally, HTTP/2 also enables more efficient processing of messages through use of binary message framing.
What are the key differences to HTTP/1.x?
What are the key differences to HTTP/1.x?
At a high level, HTTP/2:
is binary, instead of textual
is fully multiplexed, instead of ordered and blocking
can therefore use one connection for parallelism
uses header compression to reduce overhead
allows servers to “push” responses proactively into client caches
Reference
Reference
https://images.app.goo.gl/a2ENrh3vB5JLeTky7
https://en.wikipedia.org/wiki/HTTP/2
https://tools.ietf.org/html/rfc7540
https://http2.github.io/faq/
https://images.app.goo.gl/g1ZPkHCNMpsJGykC6
https://images.app.goo.gl/9LkBUvU1J5Xs1Qqk7
Page updated
Google Sites
Report abuse