Question

How do I configure SPDY in Ubuntu 12.04 / apache 2.2.22 ?

Hi, I’m trying to configure SPDY in my droplet (Apache, Ubuntu 12.04) I’m following google’s documentation, and I did exactly all steps detailed: https://developers.google.com/speed/spdy/mod_spdy/

“ht2check” website says it’s activated. Here’s the link for that:

https://www.h2check.org/

However, this chrome extension says “NOT SPDY enabled”

https://chrome.google.com/webstore/detail/http2-and-spdy-indicator/mpbpobfflnpcgagjijhmgnchggcjblin

I tried hundreds of changes on config files. Different urls, and certificates.

Any ideas of what’s going on ?


Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

Installing mod_spdy on Ubuntu 12.04 with Apache should be as simple as running the following commands if you already have SSL setup correctly.

wget https://dl-ssl.google.com/dl/linux/direct/mod-spdy-beta_current_amd64.deb
sudo dpkg -i mod-spdy-beta_current_amd64.deb
sudo a2enmod spdy
sudo service apache2 restart

Though, it appears that Google Chrome is no longer compatible with the version of mod_spdy that is available for download. It only supports the SPDY/3.1 protocol while the package provides SPDY/3. It’s also worth noting that Google is no longer developing mod-spdy and will soon be dropping support in Chrome altogether in favor of HTTP/2. See:

So you might want to consider using HTTP/2 instead.