Followed this tutorial: http://www.howtoforge.com/using-mod_spdy-with-apache2-on-debian-squeeze 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: https://cloud.premaman.co.za Found a few things in my error logs: I followed that link and found this: 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?
That is really weird, I just tried again and you are right. I haven't changed anything since posting here. Ok, well, lets leave it at that but does this look like its bad or can I just ignore it? Rings any bells with you? Can I also add a slightly related question: If I have a site where I only need HTTPS for maybe 3 URLs (i.e. a shopping cart, checkout, etc.) is it best to keep only those pages secured or rather go with the whole site for HTTPS? Speed-wise is a non-https page or a https-page with mod_spdy and the proper browser faster for the end user?
I haven't tested this. But in general a https page (without SPDY) takes a bit longer than a http page because of the SSL handshake, but after the handshake is done, subsequent pages are almost equally fast.
It is posible to install mod-spdy, apache2, in debian 8 jessie? I followed same tutorial and get: # /etc/init.d/apache2 restart [....] Restarting apache2 (via systemctl): apache2.serviceJob for apache2.service failed. See 'systemctl status apache2.service' and 'journalctl -xn' for details. failed!
Ooh, ooh, Thanks gOOver, how then to deploy a spdy server? Got these in https://spdycheck.org/ Missing NPN Extension in SSL/TLS Handshake Sorry, but this server is not including an NPN Entension during the SSL/TLS handshake. The NPN Extension is an additional part of the SSL/TLS ServerHello message which allows web servers to tell browsers they support additional protocols, like SPDY. SSL/TLS servers that don't use send the NPN Extension cannot use SPDY because they have no way to tell the browser to use SPDY instead of HTTP. SPDY Capable Server Detected! Well awesome! This SSL/TLS web server is identifying itself as Apache/2.4.10 (Debian). This is a SPDY capable web server! Go check your server for modules or newer versions which have SPDY support enabled.
