Is mod_spdy only for SSL?

[Ronneil Camara]

I tried it today on my local VM machine and chrome. I went to my test page via http but I didn't see my domain in the chrome://net-internals/#spdy

However, when I change the protocol to https, my domain was placed in the spdy table.

So, is spdy only for SSL?

[Matthew Steele]

Short answer: Yes.

Longer answer: The SPDY spec itself says nothing about SSL; however, in practice, SPDY is only ever deployed over port 443, because 1) some transparent HTTP proxies will attempt to modify data sent over port 80, and will break things if non-HTTP protocols are sent over that port, and 2) many firewalls block all ports other than 80 and 443.  Moreover, using SSL conveniently allows the client and server to easily negotiate whether to use SPDY or HTTP (or some other future protocol) during the SSL handshake.  So effectively, yes, SPDY is https-only.

 

Hope that helps,

-Matthew

[Ronneil Camara]

Thanks a lot Matthew. I was under the impression that SPDY was built because HTTP 1.0 and 1.1 are slow, and SPDY was very fast due to single connection that it creates.

[Laila Krishnan]

Hi

I am testing mod-spdy with tcp-fastopen. It works fine with spdy3.
I use Chrome browser with enable-tcp-fastopen

When I try spdy/3 without ssl (for testing purposes). with enable-tcp-fastopen and in the
httpd.conf file I tried both SpdyDebugUseSpdyForNonSslConnections 3,
I get the message  "Web page not available".

In this case, without ssl, spdy/3 works. But the problem comes when I enable tcp-fastopen with Spdy/3 or Spdy/2 without ssl.
Your suggestion is greatly appreciated.
Best regards
laila