Using mod_spdy With Apache2 On Debian Squeeze probs

Discussion in 'HOWTO-Related Questions' started by Ovidiu, Jul 9, 2012.

  1. Ovidiu

    Ovidiu Active Member

    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?
     
  2. falko

    falko Super Moderator ISPConfig Developer

    It's working for me when I go to your site.
     
  3. Ovidiu

    Ovidiu Active Member

    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?
     
  4. falko

    falko Super Moderator ISPConfig Developer

    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.
     
: debian, mod_spdy

Share This Page