On Mon, 2012-02-06 at 10:13 -0800, Chris Peterson wrote:
> > This note is basically meant to flag that something about your
> > gmail/gdocs/g+/encrypted-search handling is about to change. If you
> > see something amiss then send me mail or cc me in bugzilla as apropos.
> Is there a list of SPDY sites we should focus our testing on? Do all
> Google properties support SPDY (if specifying https)?
I believe they all do. beyond google, https://spdy-twitlog.indutny.com/
is a node.js spdy instance that can be used to confirm your browser is
up to the spdy task.
A couple google services tend to redirect you away from https (youtube
iirc), but for the most part they all do spdy over https.
Notably, if you are logged into a google account you will be redirected
from http:// to https:// (and thus potentially spdy) when you go to the
search page which is something mostly great they've been doing for a few
An unpleasant twist, unrelated to spdy, on that means that the search
dialog in firefox does this redirect too - so you take a extra round
trip for the redirect AND your search is sent in plaintext first, which
is clearly suboptimal. (633773 has the backstory on why we don't just
send it in https to start with, and that bug is a better place for that
line of discussion than this spdy thread imo.)