{"id":23494,"date":"2015-02-09T21:34:07","date_gmt":"2015-02-09T19:34:07","guid":{"rendered":"https:\/\/mamchenkov.net\/wordpress\/?p=23494"},"modified":"2015-02-09T21:34:07","modified_gmt":"2015-02-09T19:34:07","slug":"hello-http2-goodbye-spdy","status":"publish","type":"post","link":"https:\/\/mamchenkov.net\/wordpress\/2015\/02\/09\/hello-http2-goodbye-spdy\/","title":{"rendered":"Hello HTTP\/2, Goodbye SPDY"},"content":{"rendered":"<!-- google_ad_section_start -->\n<p><a href=\"http:\/\/blog.chromium.org\/2015\/02\/hello-http2-goodbye-spdy-http-is_9.html\">Chromium blog reports<\/a> that by the early next year, Chromium (and Chrome) will phase out the support for SPDY and NPN in favor of HTTP\/2 and ALPN.<\/p>\n<blockquote><p><a href=\"https:\/\/en.wikipedia.org\/wiki\/Hypertext_Transfer_Protocol\">HTTP<\/a> is the fundamental networking protocol that powers the web. The majority of sites use version 1.1 of HTTP, which was defined in 1999 with <a href=\"https:\/\/tools.ietf.org\/html\/rfc2616\">RFC2616<\/a>. A lot has changed on the web since then, and a new version of the protocol named <a href=\"https:\/\/tools.ietf.org\/html\/draft-ietf-httpbis-http2-16\">HTTP\/2<\/a> is well on the road to standardization. We plan to gradually roll out support for HTTP\/2 in Chrome 40 in the upcoming weeks.<\/p>\n<p>HTTP\/2\u2019s primary changes from HTTP\/1.1 focus on improved performance. Some <a href=\"http:\/\/daniel.haxx.se\/http2\/\">key features <\/a>such as multiplexing, header compression, prioritization and protocol negotiation evolved from work done in an earlier open, but non-standard protocol named <a href=\"https:\/\/blog.chromium.org\/2009\/11\/2x-faster-web.html\">SPDY<\/a>. Chrome has supported SPDY since Chrome 6, but since most of the benefits are present in HTTP\/2, it\u2019s time to say goodbye. We plan to remove support for SPDY in early 2016, and to also remove support for the TLS extension named <a href=\"https:\/\/tools.ietf.org\/html\/draft-agl-tls-nextprotoneg-04\">NPN<\/a> in favor of <a href=\"https:\/\/tools.ietf.org\/html\/rfc7301\">ALPN<\/a> in Chrome at the same time. Server developers are strongly encouraged to <a href=\"https:\/\/github.com\/http2\/http2-spec\/wiki\/Implementations\">move to<\/a> HTTP\/2 and ALPN.<\/p><\/blockquote>\n<!-- google_ad_section_end -->\n","protected":false},"excerpt":{"rendered":"<!-- google_ad_section_start -->\n<p>Chromium blog reports that by the early next year, Chromium (and Chrome) will phase out the support for SPDY and NPN in favor of HTTP\/2 and ALPN. HTTP is the fundamental networking protocol that powers the web. The majority of sites use version 1.1 of HTTP, which was defined in 1999 with RFC2616. A lot &hellip; <a href=\"https:\/\/mamchenkov.net\/wordpress\/2015\/02\/09\/hello-http2-goodbye-spdy\/\" class=\"more-link\">Continue reading <span class=\"screen-reader-text\">Hello HTTP\/2, Goodbye SPDY<\/span><\/a><\/p>\n<!-- google_ad_section_end -->\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"Hello HTTP\/2, Goodbye SPDY #WebDev #HTTP #browsers","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2},"_links_to":"","_links_to_target":""},"categories":[1,62,1334],"tags":[20,3225,3296,3295,1330],"keyring_services":[],"class_list":["post-23494","post","type-post","status-publish","format-standard","hentry","category-general","category-technology","category-web-work","tag-browsers","tag-http","tag-protocols","tag-spdy","tag-web-development"],"aioseo_notices":[],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack-related-posts":[{"id":21759,"url":"https:\/\/mamchenkov.net\/wordpress\/2014\/05\/07\/http2-explained\/","url_meta":{"origin":23494,"position":0},"title":"http2 explained","author":"Leonid Mamchenkov","date":"May 7, 2014","format":"link","excerpt":"http2 explained - This document describes http2 at a technical and protocol level. Background, the protocol, the implementations and the future. Some highlights: The http2 spec is expected to ship in June 2014 (a month or two away!) http2 is heavily based on Google's SPDY http2 is binary http2 fixes\u2026","rel":"","context":"In &quot;All&quot;","block_context":{"text":"All","link":"https:\/\/mamchenkov.net\/wordpress\/category\/general\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":18411,"url":"https:\/\/mamchenkov.net\/wordpress\/2013\/06\/28\/google-adds-quic-protocol-to-latest-chrome-build-delivering-http-over-udp\/","url_meta":{"origin":23494,"position":1},"title":"Google adds QUIC protocol to latest Chrome build, delivering HTTP over UDP","author":"Leonid Mamchenkov","date":"June 28, 2013","format":"link","excerpt":"Google adds QUIC protocol to latest Chrome build, delivering HTTP over UDP Here are the QUIC highlights Google wants to emphasize right now: High security similar to TLS. Fast (often 0-RTT) connectivity similar to TLS Snapstart combined with TCP Fast Open. Packet pacing to reduce packet loss. Packet error correction\u2026","rel":"","context":"In &quot;All&quot;","block_context":{"text":"All","link":"https:\/\/mamchenkov.net\/wordpress\/category\/general\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":23003,"url":"https:\/\/mamchenkov.net\/wordpress\/2014\/11\/25\/nginx-and-spdy\/","url_meta":{"origin":23494,"position":2},"title":"Nginx and SPDY","author":"Leonid Mamchenkov","date":"November 25, 2014","format":"status","excerpt":"I just popped my SPDY cherry. \u00a0And with Nginx too. Looking at a shiny A+ rating from SSL Labs for a project that is about to go live...","rel":"","context":"In &quot;All&quot;","block_context":{"text":"All","link":"https:\/\/mamchenkov.net\/wordpress\/category\/general\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":29021,"url":"https:\/\/mamchenkov.net\/wordpress\/2018\/11\/24\/some-notes-about-http-3\/","url_meta":{"origin":23494,"position":3},"title":"Some notes about HTTP\/3","author":"Leonid Mamchenkov","date":"November 24, 2018","format":false,"excerpt":"Robert Graham shares some notes about HTTP\/3.\u00a0 The whole blog post is well worth the read.\u00a0 Here are some of my favorite bits. Google is in control of future web protocol development: Google (pbuh) has both the most popular web browser (Chrome) and the two most popular websites (#1 Google.com\u2026","rel":"","context":"In &quot;All&quot;","block_context":{"text":"All","link":"https:\/\/mamchenkov.net\/wordpress\/category\/general\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":22398,"url":"https:\/\/mamchenkov.net\/wordpress\/2014\/08\/19\/https-availability-affects-websites-google-ranking\/","url_meta":{"origin":23494,"position":4},"title":"HTTPS availability affects website&#8217;s Google ranking","author":"Leonid Mamchenkov","date":"August 19, 2014","format":false,"excerpt":"Google has been pushing for wider HTTPS adoption for a while now - converting its own services, working on the SPDY\/HTTP 2.0 protocols, etc. \u00a0Now, it seems, they want other people to start adopting HTTPS too. \u00a0And what's better way than add it as a signal to Google Search rankings?\u2026","rel":"","context":"In &quot;All&quot;","block_context":{"text":"All","link":"https:\/\/mamchenkov.net\/wordpress\/category\/general\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":25965,"url":"https:\/\/mamchenkov.net\/wordpress\/2016\/03\/23\/good-bye-google-chrome-hello-chromium\/","url_meta":{"origin":23494,"position":5},"title":"Good bye Google Chrome, hello Chromium","author":"Leonid Mamchenkov","date":"March 23, 2016","format":false,"excerpt":"Google dropped the support of its Google Chrome browser on 32-bit Linux operating systems. \u00a0This is very unfortunate, but not deadly. \u00a0This change doesn't affect the Chromium browser - the Open Source project behind Google Chrome. The two are very compatible. \u00a0In fact, if you use the Google Sync in\u2026","rel":"","context":"In &quot;All&quot;","block_context":{"text":"All","link":"https:\/\/mamchenkov.net\/wordpress\/category\/general\/"},"img":{"alt_text":"Chromium-vs-Google-Chrome","src":"https:\/\/i0.wp.com\/mamchenkov.net\/wordpress\/wp-content\/uploads\/2016\/03\/Chromium-vs-Google-Chrome-500x247.jpg?resize=350%2C200&ssl=1","width":350,"height":200},"classes":[]}],"jetpack_sharing_enabled":true,"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/mamchenkov.net\/wordpress\/wp-json\/wp\/v2\/posts\/23494","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/mamchenkov.net\/wordpress\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/mamchenkov.net\/wordpress\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/mamchenkov.net\/wordpress\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/mamchenkov.net\/wordpress\/wp-json\/wp\/v2\/comments?post=23494"}],"version-history":[{"count":0,"href":"https:\/\/mamchenkov.net\/wordpress\/wp-json\/wp\/v2\/posts\/23494\/revisions"}],"wp:attachment":[{"href":"https:\/\/mamchenkov.net\/wordpress\/wp-json\/wp\/v2\/media?parent=23494"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/mamchenkov.net\/wordpress\/wp-json\/wp\/v2\/categories?post=23494"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/mamchenkov.net\/wordpress\/wp-json\/wp\/v2\/tags?post=23494"},{"taxonomy":"keyring_services","embeddable":true,"href":"https:\/\/mamchenkov.net\/wordpress\/wp-json\/wp\/v2\/keyring_services?post=23494"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}