MaxCDN Blog

Now Serving: SPDY 3.1

May 20, 2014

We are happy to announce today that MaxCDN is rolling out official SPDY support to all of our customers. It is disabled by default and all you have to do is enable it in your Pull Zone settings in our Control Panel.  If you are using the API you can also enable SPDY on your Pull Zone(s) by updating the spdy parameter to a value of 1.


What is SPDY?

SPDY is a protocol developed by Google for web content delivery. SPDY manipulates web traffic, with particular goals of reducing web page load latency and improving web security.

It can be enabled for all HTTPS traffic and the main feature that we are most excited about is the speed boost that it provides. Being a CDN company this is very important for us and we can’t wait to see our clients use it in the wild.

With the help of MaxCDN, the SPDY 3.1 module for Nginx was under development for quite some time, but finally it reached maturity and was released in Nginx mainline 1.6. It means that is now part of the stable Nginx version which makes it safe to enable in production environment.

SPDY is supported by all latest versions of Chrome, Opera and Firefox. Including their mobile editions. But even if a user’s browser does not support it its not a big deal as our servers will fallback to HTTP/1.1 with TLS for all non-compatible browsers.

  • Peter Nikolow

    This is great news. I’m curious to see SPDY in HTTP 2.0

  • Ossy

    Is it fair to say that having static resources delivered by a CDN won’t allow the main site to use the “Server Push and Server Hints” capabilities? When the Google folks designed SPDY did they actually think about CDNs? If that is the case, the only way for a CDN provider to deliver full performance via SPDY, is to take on the first page request and act as an App Accelerator.