<story><title>Your Chrome browser might not be using HTTP anymore</title><url>http://www.igvita.com/2011/04/07/life-beyond-http-11-googles-spdy</url></story><parent_chain></parent_chain><comment><author>tiles</author><text>The transparency with which Chrome did this was actually a problem for me. Google Docs/GMail did not work for months on my school&apos;s ethernet connection until I read about SPDY being implemented; sure enough, launching Chrome with SPDY disabled fixed the issue, and that requires a command line option. I wish Chrome were less transparent about this and added a few Preferences options, at least.</text></comment>
<story><title>Your Chrome browser might not be using HTTP anymore</title><url>http://www.igvita.com/2011/04/07/life-beyond-http-11-googles-spdy</url></story><parent_chain></parent_chain><comment><author>Erwin</author><text>You can peek into your Chrome&apos;ss current SPDY connections (and other interesting internals) in their internal pages:&lt;p&gt;chrome://net-internals/#events&amp;#38;q=type:SPDY_SESSION%20is:active</text></comment>