# Any rough ETA on SPDY/3 & push? **URL:** \ **Category:** NGINX\ **Created:** [October 14, 2013, 6:01pm UTC](https://www.ruby-forum.com/t/any-rough-eta-on-spdy-3-push/236958 "2013-10-14T18:01:56Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![alcina](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/a587f6/32.png) [@alcina](https://www.ruby-forum.com/u/alcina)\ **Post date:** [October 14, 2013, 6:01pm UTC](https://www.ruby-forum.com/t/any-rough-eta-on-spdy-3-push/236958/1 "2013-10-14T18:01:56Z")
Contemplating switching my site over to Jetty to take advantage of spdy/3 and push, but would rather stay with nginx really… Is there a “rough” ETA on spdy3 in nginx? 1 month? 6 months? 2 years? Thanks, sorry if this is a frequent request… Posted at Nginx Forum: > **[Any rough ETA on SPDY/3 & push?](https://forum.nginx.org/read.php?2,243684,243684#msg-243684)** > > Contemplating switching my site over to Jetty to take advantage of spdy/3 and push, but would rather stay with nginx really... Is there a "rough" ETA on spdy3 in nginx? 1 month? 6 months? 2 years? Thanks, sorry if this is a frequent... ---
**Author:** ![codemonkey](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/9fc348/32.png) [@codemonkey](https://www.ruby-forum.com/u/codemonkey)\ **Post date:** [October 14, 2013, 6:38pm UTC](https://www.ruby-forum.com/t/any-rough-eta-on-spdy-3-push/236958/2 "2013-10-14T18:38:45Z")
On Oct 14, 2013, at 8:01 PM, codemonkey [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote: > Contemplating switching my site over to Jetty to take advantage of spdy/3 > and push, but would rather stay with nginx really… > > Is there a “rough” ETA on spdy3 in nginx? 1 month? 6 months? 2 years? > > Thanks, sorry if this is a frequent request… It is! Considering it, but frankly, for a better ETA wouldn’t reject a corporate sponsor if there’s anybody here who’d be open to sponsoring an implementation similar to > **[Nginx, SPDY, and Automattic](https://barry.blog/2012/06/16/nginx-spdy-and-automattic/)** > > Yesterday, Valentin Bartenev, a developer at Nginx, Inc., announced SPDY support for the Nginx web server. SPDY is a next-generation networking protocol developed by Google and focused on making th… 🙂 ---
**Author:** ![codemonkey](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/9fc348/32.png) [@codemonkey](https://www.ruby-forum.com/u/codemonkey)\ **Post date:** [October 20, 2013, 2:08am UTC](https://www.ruby-forum.com/t/any-rough-eta-on-spdy-3-push/236958/3 "2013-10-20T02:08:53Z")
On 10/14/2013 9:37 AM, Andrew A. wrote: > Considering it, but frankly, for a better ETA wouldn’t reject a corporate > sponsor > if there’s anybody here who’d be open to sponsoring an implementation similar to > > [Nginx, SPDY, and Automattic – Barry on WordPress](http://barry.wordpress.com/2012/06/16/nginx-spdy-and-automattic/) How much capital would you need to do this? I’d contribute to a crowd-funding campaign for this and I can likely get work to match or beat what I put in. ---
**Author:** ![codemonkey](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/9fc348/32.png) [@codemonkey](https://www.ruby-forum.com/u/codemonkey)\ **Post date:** [October 22, 2013, 9:37am UTC](https://www.ruby-forum.com/t/any-rough-eta-on-spdy-3-push/236958/4 "2013-10-22T09:37:56Z")
On 10/19/2013 5:07 PM, Darren P. wrote: > On 10/14/2013 9:37 AM, Andrew A. wrote: > > > [Nginx, SPDY, and Automattic – Barry on WordPress](http://barry.wordpress.com/2012/06/16/nginx-spdy-and-automattic/) > > How much capital would you need to do this? I’d contribute to a > crowd-funding campaign for this and I can likely get work to match or > beat what I put in. I was quite serious about this offer. Is it some kind of faux pas throwing money at an open source project? ---
**Author:** ![codemonkey](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/9fc348/32.png) [@codemonkey](https://www.ruby-forum.com/u/codemonkey)\ **Post date:** [October 22, 2013, 10:28am UTC](https://www.ruby-forum.com/t/any-rough-eta-on-spdy-3-push/236958/5 "2013-10-22T10:28:10Z")
On Oct 22, 2013, at 11:37 AM, Darren P. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote: > On 10/19/2013 5:07 PM, Darren P. wrote: > > > On 10/14/2013 9:37 AM, Andrew A. wrote: > > > > > [Nginx, SPDY, and Automattic – Barry on WordPress](http://barry.wordpress.com/2012/06/16/nginx-spdy-and-automattic/) > > > > How much capital would you need to do this? I’d contribute to a > > crowd-funding campaign for this and I can likely get work to match or > > beat what I put in. > > I was quite serious about this offer. Is it some kind of faux pas throwing > money at an open source project? It isn’t. Let’s move if off the list, though, as it’s a topic which is separate from technical discussions 🙂 ---
**Author:** ![codemonkey](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/9fc348/32.png) [@codemonkey](https://www.ruby-forum.com/u/codemonkey)\ **Post date:** [November 15, 2013, 1:32am UTC](https://www.ruby-forum.com/t/any-rough-eta-on-spdy-3-push/236958/6 "2013-11-15T01:32:46Z")
> spdy/2 support has been removed from the Firefox code base ( > [912550 - remove spdy/2 support](https://bugzilla.mozilla.org/show_bug.cgi?id=912550) ) and \>= Firefox 27 will > only support \>= spdy/3. Firefox 27 will be released in January 2014 ( > [https://wiki.mozilla.org/RapidRelease/Calendar](https://wiki.mozilla.org/RapidRelease/Calendar) ) so there is some urgency in > getting spdy/3(.1) support into nginx. Just the heads up: It seems the latest Chrome beta (32.0.1700.14) has also removed support for spdy/2. Spdy is no longer enabled in Chrome on nginx-based sites, and all sites that do work run spdy/3 or later (according to chrome://net-internals/#spdy). ---
**Author:** ![codemonkey](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/9fc348/32.png) [@codemonkey](https://www.ruby-forum.com/u/codemonkey)\ **Post date:** [October 28, 2013, 1:09pm UTC](https://www.ruby-forum.com/t/any-rough-eta-on-spdy-3-push/236958/7 "2013-10-28T13:09:11Z")
spdy/2 support has been removed from the Firefox code base ( [912550 - remove spdy/2 support](https://bugzilla.mozilla.org/show_bug.cgi?id=912550) ) and \>= Firefox 27 will only support \>= spdy/3. Firefox 27 will be released in January 2014 ( [https://wiki.mozilla.org/RapidRelease/Calendar](https://wiki.mozilla.org/RapidRelease/Calendar) ) so there is some urgency in getting spdy/3(.1) support into nginx. Posted at Nginx Forum: > **[Re: Any rough ETA on SPDY/3 & push?](https://forum.nginx.org/read.php?2,243684,244199#msg-244199)** > > Contemplating switching my site over to Jetty to take advantage of spdy/3 and push, but would rather stay with nginx really... Is there a "rough" ETA on spdy3 in nginx? 1 month? 6 months? 2 years? Thanks, sorry if this is a frequent... ---
**Author:** ![codemonkey](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/9fc348/32.png) [@codemonkey](https://www.ruby-forum.com/u/codemonkey)\ **Post date:** [November 15, 2013, 5:59am UTC](https://www.ruby-forum.com/t/any-rough-eta-on-spdy-3-push/236958/8 "2013-11-15T05:59:44Z")
Hey, > > spdy/2 support has been removed from the Firefox code base ( > > [912550 - remove spdy/2 support](https://bugzilla.mozilla.org/show_bug.cgi?id=912550) ) and \>= Firefox 27 will > > only support \>= spdy/3. Firefox 27 will be released in January 2014 ( > > [https://wiki.mozilla.org/RapidRelease/Calendar](https://wiki.mozilla.org/RapidRelease/Calendar) ) so there is some urgency in > > getting spdy/3(.1) support into nginx. > > Just the heads up: It seems the latest Chrome beta (32.0.1700.14) has > also removed support for spdy/2. Spdy is no longer enabled in Chrome on > nginx-based sites, and all sites that do work run spdy/3 or later > (according to chrome://net-internals/#spdy). Actually, after some convincing [0], both Firefox [1] & Chrome [2] guys were nice enough to give us a bit more time and revert those changes, so SPDY/2 will stay around for one more release cycle (and be retired in late February). [0] [https://groups.google.com/d/msg/spdy-dev/XDudMZSq3e4/oqklqhoouAsJ](https://groups.google.com/d/msg/spdy-dev/XDudMZSq3e4/oqklqhoouAsJ) [1] [912550 - remove spdy/2 support](https://bugzilla.mozilla.org/show_bug.cgi?id=912550) [2] [318651 - chromium - An open-source project to help move the web forward. - Monorail](https://code.google.com/p/chromium/issues/detail?id=318651) Best regards, Piotr S. ---
**Author:** ![codemonkey](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/9fc348/32.png) [@codemonkey](https://www.ruby-forum.com/u/codemonkey)\ **Post date:** [November 26, 2013, 9:43pm UTC](https://www.ruby-forum.com/t/any-rough-eta-on-spdy-3-push/236958/9 "2013-11-26T21:43:57Z")
Ist there any new spdy code available for testing? I can’t find any new code in the version control since spdy/2. Since RHEL 6.5 / Centos 6.5 (currently building but openssl 1.0.1 available in CR repro) this major distibutions are also capable to run spdy. Posted at Nginx Forum: > **[Re: Any rough ETA on SPDY/3 & push?](https://forum.nginx.org/read.php?2,243684,244984#msg-244984)** > > Contemplating switching my site over to Jetty to take advantage of spdy/3 and push, but would rather stay with nginx really... Is there a "rough" ETA on spdy3 in nginx? 1 month? 6 months? 2 years? Thanks, sorry if this is a frequent...