SPDY

HTTP/2 was first discussed when it became apparent that SPDY was gaining traction with implementers (like Mozilla and nginx), and was showing significant improvements over HTTP/1.x. After a call for proposals and a selection process, SPDY was chosen as the basis for HTTP/2. Since then, there have been a number of changes, based on discussion in the Working Group and feedback from implementers.

{{As of|2012|07}}, the group developing SPDY stated publicly that it was working toward standardisation (available as an Internet Draft). The first draft of HTTP/2 used SPDY as the working base for its specification draft and editing.{{cite web|last=Nottingham|first=Mark|title=First draft of HTTP/2|url=http://lists.w3.org/Archives/Public/ietf-http-wg/2012OctDec/0447.html|work=HTTP Working Group Mailing List|access-date=2 December 2012}} The IETF working group for HTTPbis has released the draft of HTTP/2. SPDY (draft-mbelshe-httpbis-spdy-00) was chosen as the starting point.{{cite web|title=Fwd: [new-work] WG Review: Hypertext Transfer Protocol Bis (httpbis)|url=http://lists.w3.org/Archives/Public/ietf-http-wg/2012JulSep/1282.html}}{{cite news|date=2012-04-28|title=HTTPbis Working Group Start To Consider HTTP/2.0|work=InfoQ|url=http://www.infoq.com/news/2012/04/http-next|access-date=2012-08-09}}

Throughout the process, the core developers of SPDY have been involved in the development of HTTP/2, including both Mike Belshe and Roberto Peon.

Chromium, Mozilla Firefox, Opera, Amazon Silk, Internet Explorer, and Safari expressed support for SPDY at the time.

In February 2015, Google announced that following ratification of the HTTP/2 standard, support for SPDY would be deprecated, and that support for SPDY would be withdrawn.{{cite web|author1=Chris Bentzel|author2=Bence Béky|name-list-style=amp|date=9 February 2015|title=Hello HTTP/2, Goodbye SPDY|url=https://blog.chromium.org/2015/02/hello-http2-goodbye-spdy.html}} On May 15, 2015, HTTP/2 was officially ratified as {{IETF RFC|7540}}.

On February 11, 2016, Google announced that Chrome would no longer support SPDY after May 15, 2016, the one-year anniversary of {{IETF RFC|7540}} which standardized HTTP/2.{{cite web|author=Béky, Bence|date=February 11, 2016|title=Transitioning from SPDY to HTTP/2|url=https://blog.chromium.org/2016/02/transitioning-from-spdy-to-http2.html|access-date=February 12, 2016}}

On January 25, 2019, Apple announced that SPDY would be deprecated in favor of HTTP/2, and would be removed in future releases.{{Cite web|last=Marshall|first=Scott|date=2019-01-25|title=Removing Legacy SPDY Protocol Support|url=https://webkit.org/blog/8569/removing-legacy-spdy-protocol-support/|access-date=2019-03-07|website=WebKit}}

Google removed SPDY support in Google Chrome 51 which was released in 2016.{{Cite web|title=Transitioning from SPDY to HTTP/2|url=https://blog.chromium.org/2016/02/transitioning-from-spdy-to-http2.html|access-date=2022-02-05|website=Chromium Blog|language=en}} Mozilla removed it in Firefox 50.{{cite web|title=1287132 - Disable SPDY 3.1|url=https://bugzilla.mozilla.org/show_bug.cgi?id=1287132|website=bugzilla.mozilla.org}} Apple has deprecated the technology in macOS 10.14.4 and iOS 12.2.

{{update section|date=February 2022|reason=SPDY was removed from all major implementations in favor of HTTP/2}}

SPDY is a versioned protocol. SPDY control frames contain 15 dedicated bits to indicate the version of protocol used for the current session.[https://dev.chromium.org/spdy/spdy-protocol/spdy-protocol-draft2 SPDY Protocol - Draft 2]: "Currently, the only valid string is "spdy/2" (spdy/1 isn't implemented anywhere anymore)".

• Version 1: version 1 of the SPDY protocol is not used anymore.
• Version 2: soon{{As of?|date=June 2024}} to be discontinued. Nginx supports SPDY/2 in versions prior to 1.5.10.{{cite web|title=Module ngx_http_spdy_module|url=http://nginx.org/en/docs/http/ngx_http_spdy_module.html|access-date=2014-06-03|publisher=Nginx.org}} Firefox 28 and recent versions of Chrome drop support for it.{{cite web|date=2013-10-03|title=Issue 303957 - chromium — Make Chrome support only SPDY/3 and above — An open-source project to help move the web forward. - Google Project Hosting|url=https://code.google.com/p/chromium/issues/detail?id=303957|access-date=2014-02-19}} OpenLiteSpeed 1.1 and up support SPDY/2.[http://blog.litespeedtech.com/2013/06/20/openlitespeed-1-1-with-spdy/ OpenLiteSpeed 1.1 (With SPDY!)] Retrieved 2013-08-12.
• Version 3: SPDY v3 introduced support for flow control, updated the compression dictionary, and removed wasted space from certain frames, along with other minor bug fixes. Firefox supports SPDY v3 in Firefox 15. OpenLiteSpeed 1.1 and up support SPDY/3.
• Version 3.1: SPDY v3.1 introduced support for session-layer flow control, and removed the CREDENTIALS frame (and associated error codes).{{cite web|title=SPDY Protocol — Draft 3.1|url=https://www.chromium.org/spdy/spdy-protocol/spdy-protocol-draft3-1|access-date=17 November 2013}} Firefox 27 has added SPDY 3.1 support. OpenLiteSpeed 1.2.7 introduces SPDY/3.1 support.[http://blog.litespeedtech.com/2013/11/26/openlitespeed-1st-web-server-to-support-spdy3-1/ OpenLiteSpeed 1st Web Server to Support SPDY/3.1!] Retrieved 2014-1-10. Nginx 1.5.10 supports SPDY/3.1.[http://nginx.com/news/nginx-announces-support-spdy31/ NGINX Announces Support for SPDY/3.1] Retrieved 2014-02-04. F5 BIGIP 11.6 supports SPDY/3.1.[https://support.f5.com/kb/en-us/products/big-ip_ltm/releasenotes/product/relnote-ltm-11-6-0.html F5 Bigip 11.6.0 Release Notes] Retrieved 2015-03-10.
• Version 4.0: SPDY v4 alpha3 is more closely aligned with the HTTP/2 draft; it has a new stream flow control and error codes unified with the HTTP/2 draft.{{cite web|title=Upcoming SPDY/4 changes to bring it more in sync with the HTTP/2 draft|url=https://groups.google.com/d/topic/spdy-dev/EWEEWSYtlhc/discussion|access-date=27 February 2014}}

The goal of SPDY is to reduce web page load time. This is achieved by prioritizing and multiplexing the transfer of web page subresources so that only one connection per client is required. TLS encryption is nearly ubiquitous in SPDY implementations, and transmission headers are gzip- or DEFLATE-compressed by design{{cite web|title=SPDY Protocol — Draft 3|url=https://www.chromium.org/spdy/spdy-protocol/spdy-protocol-draft3|access-date=25 August 2012}} (in contrast to HTTP, where the headers are sent as human-readable text). Moreover, servers may hint or even push content instead of awaiting individual requests for each resource of a web page.

SPDY requires the use of SSL/TLS (with TLS extension ALPN) for security but it also supports operation over plain TCP. The requirement for SSL is for security and to avoid incompatibility when communication is across a proxy.

SPDY does not replace HTTP; it modifies the way HTTP requests and responses are sent over the wire. This means that all existing server-side applications can be used without modification if a SPDY-compatible translation layer is put in place.

SPDY is effectively a tunnel for the HTTP and HTTPS protocols. When sent over SPDY, HTTP requests are processed, tokenized, simplified and compressed. For example, each SPDY endpoint keeps track of which headers have been sent in past requests and can avoid resending the headers that have not changed; those that must be sent are compressed.

{{update section|date=December 2015}}

For use within HTTPS, SPDY requires the TLS extension Next Protocol Negotiation (NPN)[//tools.ietf.org/agenda/82/slides/tls-3.pdf NPN protocol and explanation about its need to tunnel SPDY over HTTPS]. or Application-Layer Protocol Negotiation (ALPN){{Cite web|title=ImperialViolet - NPN and ALPN|url=https://www.imperialviolet.org/2013/03/20/alpn.html|access-date=2021-06-08|website=www.imperialviolet.org}} thus browser and server support depends on the HTTPS library.

OpenSSL 1.0.1 or greater introduces NPN.[http://www.openssl.org/news/changelog.html Openssl 1.0.1 changelog]. Patches to add NPN support have also been written for NSS and TLSLite.[https://technotes.googlecode.com/git/nextprotoneg.html TLS Next Protocol Negotiation. Section: Implementations] {{webarchive|url=https://web.archive.org/web/20120730004302/http://technotes.googlecode.com/git/nextprotoneg.html |date=2012-07-30 }}.

Microsoft had not implemented the NPN extension in the Windows TLS/SSL Security Support Provider, preventing SPDY's inclusion in the .NET Framework. Limited HTTP/2 support was added in .NET Framework 4.6 and expanded in .NET Core.{{cite web |last1=Aagesen |first1=Jakob |title=http/2 support |url=https://learn.microsoft.com/en-us/answers/questions/1159881/http-2-support |website=Microsoft Q&A |access-date=28 May 2025}}

• Google Chrome/Chromium.[https://src.chromium.org/viewvc/chrome/trunk/src/net/spdy/ Chromium SPDY client implementation].[https://www.chromium.org/spdy/spdy-proxy-examples Chromium: SPDY proxy examples] {{Webarchive|url=https://web.archive.org/web/20170919141654/http://www.chromium.org/spdy/spdy-proxy-examples |date=2017-09-19 }}. SPDY sessions in Chrome can be inspected via the URI: chrome://net-internals/#events&q=type:SPDY_SESSION%20is:active. There is a command-line switch for Google Chrome (--[http://peter.sh/experiments/chromium-command-line-switches/#enable-websocket-over-spdy enable-websocket-over-spdy]) which enables an early, experimental implementation of WebSocket over SPDY.[http://peter.sh/experiments/chromium-command-line-switches/ List of Chromium Command Line Switches]. SPDY protocol functionality can be (de)activated by toggling "Enable SPDY/4" setting on local chrome://flags page. Chromium is expected to remove support for SPDY and Next Protocol Negotiation in early 2016, in favor of HTTP/2 and ALPN.{{cite web | url=https://blog.chromium.org/2015/02/hello-http2-goodbye-spdy.html | title=Hello HTTP/2, Goodbye SPDY | publisher=Chromium Blog | date=February 9, 2015 | access-date=9 February 2015 |author1=Bentzel, Chris |author2=Béky, Bence }} Starting with version 40.x in Feb 2015 Chrome has already dropped support for SPDY/3 and only supports SPDY/3.1 going forward. This has caused Apache websites to be without SPDY support when visited from Google Chrome.{{cite web|url=https://groups.google.com/forum/#!topic/mod-spdy-discuss/FPEj0zG5I0Y|title=Google Groups|website=groups.google.com}}
• Firefox supports SPDY 2 from version 11, and default-enabled since 13 and later. (Also SeaMonkey version 2.8+.) SPDY protocol functionality can be (de)activated by toggling the [http://kb.mozillazine.org/Network.http.spdy.enabled network.http.spdy.enabled] variable in about:config. Firefox 15 added support for SPDY 3.{{cite web|title=Firefox 15 — Release Notes|url=https://website-archive.mozilla.org/www.mozilla.org/firefox_releasenotes/en-US/firefox/15.0/releasenotes/|access-date=3 September 2012}} Firefox 27 has added SPDY 3.1 support.{{cite web | url = https://website-archive.mozilla.org/www.mozilla.org/firefox_releasenotes/en-US/firefox/27.0/releasenotes/ | title = Firefox Notes Desktop | date = 2014-02-04 | access-date = 2014-02-05}} Firefox 28 has removed support of SPDY 2.{{cite web | url = https://website-archive.mozilla.org/www.mozilla.org/firefox_releasenotes/en-US/firefox/28.0beta/releasenotes/ | title = Firefox Beta Notes — Desktop | date = 2014-02-06 | access-date = 2014-02-07}} about:networking (or the HTTP/2 and SPDY indicator add-on){{cite web|url=https://addons.mozilla.org/en-US/firefox/addon/spdy-indicator/ |title=HTTP/2 and SPDY indicator |work=Add-ons for Firefox |publisher=Mozilla |date=2014-11-26 |access-date=2015-02-12}} shows if a website uses SPDY.
• Opera browser added support for SPDY as of version 12.10.{{cite web|url=http://www.opera.com/docs/changelogs/unified/1210/|title=Opera: Opera 12.10 Changelog|author=David Honneffer, Documentation Specialist}}
• Internet Explorer 11 added support for SPDY version 3,{{cite web|url=http://microsoft-news.com/webgl-spdy3-new-dev-tools-more-confirmed-for-ie11-in-win-8-1/|title=WebGL, SPDY/3, New Dev Tools, & More Confirmed For IE11 In Win 8.1|publisher=Microsoft News}}{{cite web|url=http://blogs.msdn.com/b/ieinternals/archive/2013/09/24/internet-explorer-11-changelist-change-log.aspx|title=IE11 Changes|publisher=Microsoft}} but not for the Windows 7 version.{{cite web|url=http://winsupersite.com/windows-7/microsoft-releases-internet-explorer-11-windows-7|title=Microsoft Releases Internet Explorer 11 for Windows 7|date=2013-11-07}} A problem experienced by some users of Windows 8.1 and Internet Explorer 11 is that on initial loading, Google says "Page not found" but on reloading, it is fine. One fix for this is to disable SPDY/3 in Internet Options > Advanced.{{cite web|url=https://angrytechnician.wordpress.com/2014/01/16/google-not-loading-first-time-in-ie11-via-a-web-proxy-on-windows-8-1-turn-off-spdy-support/#more-4479 |title=Google not loading first time in IE11 via a web proxy on Windows 8.1? Turn off SPDY support. | The Angry Technician |publisher=Angrytechnician.wordpress.com |date= 2014-01-16|access-date=2014-02-19}} After version 11, IE will drop the support of SPDY, as it will adopt HTTP/2.{{cite web | url=http://blogs.msdn.com/b/ie/archive/2014/10/08/http-2-the-long-awaited-sequel.aspx | title=HTTP/2: The Long-Awaited Sequel | publisher=Microsoft | date=October 8, 2014 | access-date=8 October 2014 |author1=Rob Trace |author2=David Walp }}
• Amazon's Silk browser for the Kindle Fire uses the SPDY protocol to communicate with their EC2 service for Web pages rendering.
• Safari 8 and third-party applications in OS X 10.10 and iOS 8 adds support for SPDY 2, 3 and 3.1.{{cite web|url=http://devstreaming.apple.com/videos/wwdc/2014/707xx1o5tdjnvg9/707/707_whats_new_in_foundation_networking.pdf|title=What's New in Foundation Networking|publisher=Apple inc.|access-date=2014-07-07}}

{{As of|2021|05}}, approximately 0.1% of all websites support SPDY,{{cite web|url=http://w3techs.com/technologies/details/ce-spdy/all/all |title=Usage of SPDY for websites|access-date=2021-05-04|website=w3techs.com}} in part due to transition to HTTP/2. In 2016, NGINX and Apache{{cite web|url=https://w3techs.com/technologies/overview/web_server/all|title=Usage of web servers for websites|access-date=2016-07-26|website=w3techs.com}} were the major providers of SPDY traffic. In 2015, NGINX 1.9.5 dropped SPDY support in favor of HTTP/2.

Some Google services (e.g. Google Search, Gmail, and other SSL-enabled services) use SPDY when available.[http://groups.google.com/group/spdy-dev/browse_thread/thread/4c2396ecbc36b1c4 spdy-dev mailing list: SPDY on Google servers?]. Google's ads are also served from SPDY-enabled servers.[http://www.eweek.com/c/a/Cloud-Computing/Google-Speeds-Up-WebPage-Downloads-with-SPDY-Protocol-240303/ Google Speeds Up Web-Page Downloads with SPDY Protocol - Cloud Computing - News & Reviews]. eWeek.com (2011-06-20). Retrieved on 2013-11-21.

A brief history of SPDY support amongst major web players:

• In November 2009, Google announced SPDY as an internal project to increase the speed of the web.{{cite web|url=http://googleresearch.blogspot.com/2009/11/2x-faster-web.html|title=Research Blog: A 2x Faster Web|work=Research Blog}}
• In September 2010, Google released SPDY in Chrome 6 on all platforms.{{cite web|url=http://www.slideshare.net/ido-cotendo/from-fast-to-spdy-velocity-2011|title=From Fast to SPDY — Velocity 2011|author=Ido Safruti|date=2011-06-15}}
• In January 2011, Google deployed SPDY across all Google services.{{cite web|url=https://groups.google.com/forum/#!topic/spdy-dev/TCOW7Lw2scQ|title=Google Groups}}
• In March 2012, Twitter enabled SPDY on its servers, at the time making it the second largest site known to deploy SPDY.[http://browserfame.com/527/twitter-spdy-support Twitter Adopts SPDY] {{Webarchive|url=https://web.archive.org/web/20120311000945/http://browserfame.com/527/twitter-spdy-support |date=2012-03-11 }}.
• In March 2012, the open source Jetty Web Server announced support for SPDY in version 7.6.2 and 8.1.2,[//wiki.eclipse.org/Jetty/Feature/SPDY Jetty Feature SPDY]. while other open source projects were working on implementing support for SPDY, including Node.js,{{cite web|url=https://github.com/indutny/node-spdy |title=indutny/node-spdy · GitHub |publisher=Github.com |access-date=2012-05-10}}{{cite web|author=Fedor Indutny |url=http://blog.nodejitsu.com/what-is-node-spdy |title=What the $%@! is SPDY — blog.nodejitsu.com — scaling node.js applications one callback at a time |publisher=blog.nodejitsu.com |date=2012-01-24 |access-date=2012-05-10}} Apache (mod_spdy),{{cite web|url=https://code.google.com/p/mod-spdy/ |title=mod-spdy — Apache SPDY module — Google Project Hosting |access-date=2012-05-10}} curl,{{cite web|url=http://daniel.haxx.se/blog/2011/10/18/libspdy/ |title=libspdy |publisher=daniel.haxx.se |date=2011-10-18 |access-date=2012-05-10}} and Nginx.{{cite web|url=https://twitter.com/nginxorg/status/192301063934705665|title=@DeviaVir It's going well ;) So far we're on schedule, should hopefully be available by the end of May|work=Twitter}}
• In April 2012 Google started providing SPDY packages for Apache servers which led some smaller websites to provide SPDY support.{{cite web|url=https://developers.google.com/speed/spdy/mod_spdy/ |title=mod_spdy — mod_spdy — Google Developers |access-date=2012-05-10}}
• In May 2012 F5 Networks announced support for SPDY in its BIG-IP application delivery controllers.[http://www.f5.com/news-press-events/press/2012/20120508b.html F5 Helps Organizations Improve User Experience and Simplify Management with First Integrated SPDY Gateway | About F5 | F5 Networks] {{webarchive|url=https://web.archive.org/web/20120611083425/http://www.f5.com/news-press-events/press/2012/20120508b.html |date=2012-06-11 }}. F5.com (2012-05-08). Retrieved on 2013-11-21.
• In June 2012 Nginx open source web server announced support for SPDY.{{cite web|url=http://mailman.nginx.org/pipermail/nginx-devel/2012-June/002343.html |title=Announcing SPDY draft 2 implementation in nginx |publisher=Nginx |date=2012-06-15 |access-date=2012-06-16}}
• In July 2012 Facebook announced implementation plans for SPDY.{{cite web|last=Beaver|first=Doug|title=HTTP2 Expression of Interest|url=http://lists.w3.org/Archives/Public/ietf-http-wg/2012JulSep/0251.html|publisher=W3C|access-date=15 July 2012}} By March 2013 SPDY was implemented by some of their public web servers.{{cite news|last=Finley|first=Klint|title=Facebook Makes Itself a Bit More SPDY|newspaper=Wired|url=https://www.wired.com/wiredenterprise/2013/03/facebook-spdy/|access-date=18 March 2013}}
• In August 2012 WordPress.com announced support for SPDY (using Nginx) across all their hosted blogs.{{cite web|url=https://twitter.com/wordpressdotcom/statuses/238741078172389377 |title=Just enabled #SPDY for all http://WordPress.com/ -hosted sites. |date=2012-08-28 |access-date=2012-08-28}}
• In June 2013, LiteSpeed Technologies announced support for SPDY/2 and SPDY/3 on OpenLiteSpeed, their open source HTTP server. Support for SPDY/3.1 was announced November 2013.
• In January 2014, Synology announced SPDY is included in the new DSM 5.0.[http://www.synology.com/fr-fr/support/beta_dsm_5_0] DSM 5.0 beta
• In February 2014, CloudFlare using nginx announced automatic support for SPDY v3.1 for all customers with SSL/TLS certificates.{{cite web|author=John Graham-Cumming |url=http://blog.cloudflare.com/staying-up-to-date-with-the-latest-protocols-spdy-3-1#disqus_thread |title=Staying up to date with the latest protocols: SPDY/3.1 | CloudFlare Blog |publisher=Blog.cloudflare.com |date= 2014-02-17|access-date=2014-02-19}}
• In May 2014, MaxCDN using nginx announced support for SPDY v3.1 via customers' Pull Zone settings and their API.{{cite web|author=Justin Dorfman|url=http://blog.maxcdn.com/now-serving-spdy-3-1/ |title=Now Serving: SPDY 3.1 |publisher=blog.maxcdn.com |access-date=2014-05-20}}
• In October 2014, Yahoo shows support of SPDY on the Yahoo Homepage — www.yahoo.com
• In September 2015, the latest version of the Nginx web server dropped SPDY support in favour of HTTP/2{{cite web|url=https://www.nginx.com/blog/nginx-1-9-5/|title=HTTP/2 Supported in Open Source NGINX 1.9.5 - NGINX|date=22 September 2015}}
• In May 2016, CloudFlare releases patches to Nginx web server, the patches supports HTTP/2 and SPDY simultaneously.{{cite web|url=https://blog.cloudflare.com/open-sourcing-our-nginx-http-2-spdy-code/|title=Open sourcing our NGINX HTTP/2 + SPDY code|access-date=2016-08-05|date=2016-03-13}}

According to W3Techs, {{as of|lc=yes|2021|05}}, most SPDY-enabled websites use nginx, with the LiteSpeed web server coming second.{{cite web|title=Distribution of Web Servers among websites that use SPDY|url=http://w3techs.com/technologies/segmentation/ce-spdy/web_server|access-date=2021-05-04}}

{{Portal|Internet}}

• HTTP pipelining
• HTTP persistent connection
• HTTP Speed+Mobility
• QUIC – Another transport layer communication protocol from Google. The underlying protocol of HTTP/3.{{cite web |last1=Ghedini |first1=Alessandro |last2=Lalkaka |first2=Rustam |title=HTTP/3: the past, the present, and the future |url=https://blog.cloudflare.com/http3-the-past-present-and-future/ |website=The Cloudflare Blog |access-date=16 January 2020 |language=en |date=26 September 2019}}
• Optimized Protocol for Transport of Images to Clients (OPTIC)

{{Reflist|30em|refs=

{{cite web

| url = http://www.opera.com/press/releases/2012/11/06/

| title = Opera: Built-in support for the SPDY protocol

| access-date = 2012-11-06

}}

{{cite web

| url = http://microsoft-news.com/webgl-spdy3-new-dev-tools-more-confirmed-for-ie11-in-win-8-1/

| title = IE11 SPDY/3 confirmed

| access-date = 2013-06-25

| date = 2013-06-25

}}

{{cite web

| url = https://dev.chromium.org/spdy/spdy-whitepaper

| title = SPDY: An experimental protocol for a faster web

| work = Chromium Developer Documentation

| access-date = 2009-11-13

}}

{{cite web

| url = https://groups.google.com/group/spdy-dev/browse_thread/thread/4c2396ecbc36b1c4

| title = SPDY on Google servers?

| access-date = 2012-02-28

}}

{{cite web

| url = http://www.mnot.net/blog/2012/03/31/whats_next_for_http

| title = What's next for HTTP

| first = Mark

| last = Nottingham

| access-date = 2012-03-31

}}

{{cite web

| url = //tools.ietf.org/html/draft-mbelshe-httpbis-spdy-00

| title = SPDY Protocol on IETF

| access-date = 2012-02-08

}}

{{cite web

| url = https://blog.chromium.org/2009/11/2x-faster-web.html

| title = A 2x Faster Web

| date = 2009-11-11

| publisher = Official Google Chromium Blog

| access-date = 2009-11-13

}}

{{cite web

| url = https://arstechnica.com/web/news/2009/11/spdy-google-wants-to-speed-up-the-web-by-ditching-http.ars

| title = SPDY: Google wants to speed up the web by ditching HTTP

| author = Iljitsch van Beijnum

| work = Ars Technica

| date = 2009-11-12

| access-date = 2009-11-13

}}

{{cite web

| url = http://www.pro-linux.de/news/2009/14950.html

| date = 13 November 2009

| title = Google stellt HTTP-Alternative SPDY vor

| author = Mirko Lindner

| access-date = 2011-10-21

|language=de}}

{{cite web

| url = https://arstechnica.com/gadgets/news/2011/09/amazons-silk-web-browser-adds-new-twist-to-old-idea.ars

| title = Amazon's Silk Web browser adds new twist to old idea

| author = Ryan Paul

| date = 28 September 2011

| access-date = 2011-10-21

}}

{{cite web

| url = https://bugzilla.mozilla.org/show_bug.cgi?id=528288

| title = Mozilla Bug 528288 - Implement SPDY protocol

}}

{{cite web

| url = //www.apple.com/pr/library/2014/06/02Apple-Announces-OS-X-Yosemite.html

| title = Apple — Press Info — Apple Announces OS X Yosemite

| date = 2 June 2014

| access-date = 2014-06-02

}}

}}

• [https://www.chromium.org/spdy SPDY Documentation]
• [https://arstechnica.com/web/news/2009/11/spdy-google-wants-to-speed-up-the-web-by-ditching-http.ars SPDY: Google wants to speed up the web by ditching HTTP]
• [https://dev.chromium.org/spdy/spdy-whitepaper SPDY-Whitepaper]
• [https://code.google.com/p/mod-spdy Apache SPDY module]
• [https://www.varnish-cache.org/docs/trunk/phk/http20.html SPDY Review and Analysis]

{{Web browsers}}

Category:Internet protocols

Category:Application layer protocols

Category:Session layer protocols