{"id":5447,"date":"2015-06-12T07:00:04","date_gmt":"2015-06-12T15:00:04","guid":{"rendered":"http:\/\/formtek.com\/blog\/?p=5447"},"modified":"2015-05-05T18:07:20","modified_gmt":"2015-05-06T02:07:20","slug":"html2-blueprint-for-speedier-and-more-secure-internet-communications","status":"publish","type":"post","link":"https:\/\/formtek.com\/blog\/html2-blueprint-for-speedier-and-more-secure-internet-communications\/","title":{"rendered":"HTML\/2: Blueprint for Speedier and More Secure Internet Communications"},"content":{"rendered":"

In February 2015 an overhaul of the HTTP protocol was approved, the first change since HTTP 1.1 was adopted in 1999. \u00a0The new protocol is being called HTTP\/2.<\/p>\n

The new protocol was in development for two years by the IEFT <\/a>(Internet Engineering Task Force) and is based on a protocol created by Google called SPDY.<\/p>\n

Some of the ways in which HTTP\/2 will speed up internet communication is the compression of header information and the ability to send multiple requests over a single connection. \u00a0Web pages should load ten to forty times faster with HTTP\/2. \u00a0The improvements are expected to speed up web traffic and improve efficiency so that mobile devices will consume less power when loading browser pages.<\/p>\n

HTTP\/2 was originally intended to have TLS (Transport Layer Security) encryption, or SSL, built in, but that idea was rejected because it was felt that doing so would make implementation of the new standard much more difficult for network operators and proxy vendors.<\/p>\n

Mark Nottingham<\/a>, chair of the IETF HTTP Working Group, said that<\/a> “one of the big reasons that HTTP\/2 took so long to get to is that upgrading the protocol in the deployed infrastructure is really hard; there are lots of boxes out there that assume HTTP\/1 will never change. \u00a0So, if the transition from HTTP\/1 to HTTP\/2 goes well, it should be a lot easier to introduce the next version, because we can use the same mechanism that we used for the first big hop.”<\/p>\n

 <\/p>\n

<\/div>\n
\"Digg<\/a><\/div>
\"Reddit<\/a><\/div>
\"Stumble<\/a><\/div>
\"Buzz<\/a><\/div>
\"Vote<\/a><\/div>
\"Share<\/a><\/div>
\"Bookmark<\/a><\/div>
\"Kick<\/a><\/div>
\"Shout<\/a><\/div>
\"Share<\/a><\/div>
\"Bookmark<\/a><\/div>
\"Post<\/a><\/div>
\"Google<\/a><\/div><\/div>","protected":false},"excerpt":{"rendered":"

In February 2015 an overhaul of the HTTP protocol was approved, the first change since HTTP 1.1 was adopted in 1999. \u00a0The new protocol is being called HTTP\/2. The new protocol was in development for two years by the IEFT…<\/span><\/p>\n

Read more ›<\/a><\/div>\n

<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[36],"tags":[],"class_list":["post-5447","post","type-post","status-publish","format-standard","hentry","category-technology"],"_links":{"self":[{"href":"https:\/\/formtek.com\/blog\/wp-json\/wp\/v2\/posts\/5447","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/formtek.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/formtek.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/formtek.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/formtek.com\/blog\/wp-json\/wp\/v2\/comments?post=5447"}],"version-history":[{"count":0,"href":"https:\/\/formtek.com\/blog\/wp-json\/wp\/v2\/posts\/5447\/revisions"}],"wp:attachment":[{"href":"https:\/\/formtek.com\/blog\/wp-json\/wp\/v2\/media?parent=5447"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/formtek.com\/blog\/wp-json\/wp\/v2\/categories?post=5447"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/formtek.com\/blog\/wp-json\/wp\/v2\/tags?post=5447"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}