View Single Post
Old 9th July 2012, 10:55
Ovidiu Ovidiu is offline
Senior Member
Join Date: Sep 2005
Posts: 1,269
Thanks: 84
Thanked 25 Times in 21 Posts
Default Using mod_spdy With Apache2 On Debian Squeeze probs

Followed this tutorial:

Google Chrome doesn'T show any traces of using mod_spdy with my test site: chrome://net-internals/#spdy

Here it is if you want to try:

Found a few things in my error logs:

[Mon Jul 09 09:17:57 2012] [warn] [client] [] NPN didn't happen during SSL handshake. You're probably using a version of mod_ssl that doesn't support NPN. Without NPN support, the server cannot use SPDY. See for more information on installing a version of mod_spdy with NPN support.
[Mon Jul 09 09:34:28 2012] [warn] [client] [stream 31] [] Unsupported read mode (2) on stream 31
I followed that link and found this:

Known compatibility issues, and workarounds. Updated Apr 18, 2012 by
Since mod_spdy uses a thread pool to process multiplexed requests concurrently, it is not compatible with non-thread-safe Apache modules such as mod_php. If you use mod_php or another non-thread-safe generator, you can use it with mod_spdy by running it with mod_fcgid. We have successfully run an Apache server with SPDY, PHP and WordPress by using mod_fcgid instead of mod_php.
mod_spdy is currently not compatible with mod_ssl's SSLRequireSSL directive; see issue 31. There is no known workaround at this time except to simply not use the SSLRequireSSL directive.
Some users whose sites redirect http urls to https have experienced redirect loops after installing mod_spdy. If this happens, please see issue 34 for a workaround that may help.
I am using Debian 6.0 set up according to the ISPCFG3 how to for the perfect server and this test site is using mod_fcgid

Any hints? Do I really need to build mod_ssl with NPN support?
Reply With Quote
Sponsored Links