Jetty gets 'SPDY'

86 points by thebootstrapper 14 years ago | 11 comments

ck2 14 years ago |

Now added to the small list of SPDY enabled sites as I find them:

https://www.webtide.com/ https://twitter.com https://spdytest.com https://spdy-twitlog.indutny.com https://www.codecentric.de (and of course google.com, gmail and youtube.com)

Of course the number will explode in a few months but fun to know the handful in the "early days".

ps. SPDY indicator for Firefox 11+ https://addons.mozilla.org/en-US/firefox/addon/spdy-indicato...

steve-howard 14 years ago | |

Sadly it looks like supporting SPDY for Firefox has to be special-cased (the indicator checks for X-Firefox-Spdy: in the headers). Because of this only a couple of the above servers support it.

ck2 14 years ago | | |

@Steve, firefox itself injects that header, the server doesn't send it.

Unfortunately firefox doesn't seem to currently set any kind of accessible variable to indicate SPDY so I suggested an idea to detect that injected header for a Firefox port of the chrome indicator extension. Cheng Sun made it an hour later.

benjarrell 14 years ago | |

Why will it explode in a few months?

mhd 14 years ago | | |

Because right now you have to intentionally "hack" your server to include it, once it's part of some standard components, it will be used automatically, or at least will be easy enough to add. I think nginx is working on including it in the default setup.

vgnet 14 years ago | | |

See http://webtide.intalio.com/2012/03/jetty-spdy-is-joining-the... for a hyperbolic endorsement.

To sum it up, clients (SPDY enabled by default in FF13 and already in Chrome) and servers (Apache, nginx, Jetty, node, Google sites) are becoming available, some niches (mobile, high latency) are bound to benefit a lot and it's a good (better?) solution for the general case.

rambocoder 14 years ago | | |

It will be enabled by default in Firefox 13.

bensummers 14 years ago |

As a bonus, the "npn-boot" jar to extend the Java SSL implementation with the necessary next_protocol_negotiation extension support also allows access to the server_name extension. This should mean that you could implement server SNI support in Java, which allows SSL virtual hosting for supported clients.