6 ms·
Introducing SPDY
- nemo1618 14y agoInteresting. I wonder if moot will adopt this for 4chan. Recently he's seemed interested in optimizing the site (most notably by cleaning up the HTML/CSS and adding mobile support).
- sirn 14y ago4chan is already using CloudFlare Pro (you can check by visiting their SSL url, they're using CloudFlare cert), so it should be easy for him to enable SPDY support.
- joubert 14y agoSPDY is built on top of TLS, which means it requires a site to have a valid SSL certificate in order to work. This, unfortunately, limits SPDY only to CloudFlare's paid customers who have enabled Flexible or Full SSL support. Microsoft is working on revised IETF proposal that is SPDY-like, but removes the requirement for SSL/TLS. If the TLS requirement is removed in the future, we'll make SPDY (or whatever it comes to be called) available more broadly. Can SPDY theoretically be transitioned to not be built on top of TLS, or is the MSFT work a more likely solution?
- jgrahamc 14y agoOne of the reasons SPDY is on top of TLS is so that equipment between the browser and the server doesn't try to mess with the protocol. If SPDY were run on port 80 then there would be problems with proxies etc. Wrapping it in TLS means that it can't be snooped upon and messed with.
- afimrishi 14y agoSPDY as specced does not require TLS. However, you can see Google's WebSocket connectivity test results at http://www.ietf.org/mail-archive/web/tls/current/msg05593.html http://www.ietf.org/mail-archive/web/tls/current/msg05593.ht.... The poor connectivity over ports other than 443 is one of the strongest motivations for real deployments of SPDY over the public internet to require TLS.
- mdwelsh 14y agoSPDY does not technically require TLS, but It's the Right Thing To Do [tm]. According to Mike Belshe, there are two reasons that SPDY was designed to use TLS. The first was pragmatic: Middleboxes on the Internet wouldn't be able to pass through non-HTTP traffic, so unless a different port was used, the only way to punch through the various proxy layers was to use end-to-end security. But the other reason is just as important: It's 2012, folks. It seems insane that most Web traffic goes in the clear. Browsers are fully capable of doing the SSL handshake without incurring a major performance cost - even on mobile devices. Finally, we may not get another chance to change the web protocol stack for another 15 years, so it's best to get it right now.
- septerr 14y ago"By gathering all scripts, regardless of where they're hosted, into a single HTTP request, Rocket Loader limits the number of HTTP connections that are needed. This also means that even third party scripts that appear on your page are requested under your site's domain. " How do you do that?
- mbrubeck 14y agoCloudFlare's server acts as a proxy. It downloads each resource over HTTP from its original location and caches it, then delivers all the resources to the client over SPDY. The preceding paragraph explains it: "For SPDY support, CloudFlare acts as a gateway... We handle the multiplexing and begin sending down objects we already have in our cache. The request to the origin server for non-cached objects is sent over standard HTTP/S." This is similar to the proxy mode in Amazon's Silk browser for Kindle Fire.
- igrigorik 14y agoDo you rewrite the hosts on all third party sites to be the site domain? I'm still not following this setup. Silk is an entirely different setup. Silk (a) manually sets their SPDY gateway as a browser proxy, which is a system level setting, and (b) silk does not tunnel HTTPS requests. CloudFlare obviously doesn't have control over my browsers proxy settings, so if the page I'm loading is abc.com/page, and that page has a request to twitter.com/widget.js, then the browser should open a connection directly to twitter.com to fetch that resource. P.S. SPDY does allow tunneling HTTPS, but once again, that requires a system level proxy setup.
- moonboots 14y agoTo use cloudflare's "rocket loader", the host domain dns record must point to cloudflare instead of the origin server. If abc.com were using cloudflare, a user's request to abc.com/page would first hit cloudflare's server. Cloudflare would then proxy the request to abc's origin server, rewrite 3rd party urls, and return the modified content to the user. I'm not sure how well cloudflare handles http vary headers, e.g. 3rd party resources that serve different content depending on cookies or user agent. An example could be google web fonts which serves different css and fonts to different browsers.
- grandalf 14y agoIs cloudflare mainstream? Any testimonials? Sounds pretty cool.