Ran a SPDY test (http://spdycheck.org/) on my public openfire server
Network Server on 443
Nice, this host has a network service listening on port 443. SPDY works over SSL/TLS which listens on port 443.
Good, this host is speaking SSL/TLS. SPDY piggybacks on top of SSL/TLS, so a website needs SSL/TLS to use SPDY.
Warning! Invalid X.509 Certificate
This website is responding with an invalid X.509 certificate. The specific problem(s) with the certificate are:
. By default, most web browsers will not display content from sites with invalid certificates. Users may have trouble accessing this website and using SPDY. Use the Qualys SSL Labs SSL Server Test tool to investigate the problems with the certificate.
ServerHello Contains NPN Extension
Nice, this server including the NPN Entension during the SSL/TLS handshake. The NPN Extension is an additional part of the SSL/TLS ServerHello message which allows the web server to tell browser it supports additional protocols, like SPDY.
Success! SPDY is Enabled!
Hurray, this website is using SPDY! The following protocols are supported:
SPDY Protocol Support Update-To-Date
This website supports the latest version of SPDY, which is spdy/3.
HTTP Fallback Detected
This website is using SPDY, but it also supports traditional HTTP over SSL. This ensures that older web browsers can still access this site using HTTP
HTTP Traffic Allowed
This website can still be access via HTTP. HTTP does not provide any widely implemented mechanism for using other protocols like SPDY. Only traffic over SSL/TLS using the NPN Extension can be optimized with SPDY. By allowing HTTP traffic, this website is not even offering SPDY capable browsers the choice of using SPDY. If possible, this website should redirect all http:// to https://, ideally with a cachable HTTP 301 redirect.