MAR-2015
Page 13 of 40
Introduction
Why to revise HTTP?
On 18 Feb 2015, the new and long-awaited version of HTTP (HTTP/2) took a major step toward becoming a reality. It is been approved by Internet Engineering Steering Group (IESG) for publication as standardstrack RFCs, after more than 2 years of discussion, with more than 200 design issues, 17 drafts and 30 implementations. It's on the way to the RFC Editor, with RFC number assigned and further editorial processes before published.
Since HTTP practically only allows one outstanding request per TCP connection, loading a Web page is resource intensive, and loading all of those assets efficiently is difficult. Also, since browsers have used multiple TCP connections to issue parallel requests, it will lead to performance issues when there are many concurrent connections.
A Publication of Professional Information Security Association