Google Chrome replaces HTTP with SPDY for some Google websites

#1

Post by uiet » Mon, Aug 08, 2011, 10:36 AM UTC

Google Chrome replaces HTTP with SPDY for some Google websites
blog.alertfox.com

Re: Google Chrome replaces HTTP with SPDY for some Google websites

#2

Post by wccrawford » Mon, Aug 08, 2011, 11:02 AM UTC

I Googled but didn't find anything about SPDY with slow or unreliable connections. I wonder if it also speeds that up, or if it might actually make things worse?

Re: Google Chrome replaces HTTP with SPDY for some Google websites

#3

Post by bemmu » Mon, Aug 08, 2011, 11:08 AM UTC

Am I the only one who is constantly getting SPDY protocol errors with Chrome?

Re: Google Chrome replaces HTTP with SPDY for some Google websites

#4

Post by jannes » Mon, Aug 08, 2011, 11:25 AM UTC

bemmu wrote: post #3

Am I the only one who is constantly getting SPDY protocol errors with Chrome?

What does a SPDY protocol error look like? I don't think I have encountered one yet.

Is there any way a user can tell a SPDY and a HTTP error apart?

Re: Google Chrome replaces HTTP with SPDY for some Google websites

#5

Post by jannes » Mon, Aug 08, 2011, 11:29 AM UTC

This has been here before: http://news.ycombinator.com/item?id=2420201

I'm mentioning it because I think that source is actually much more informative.

Re: Google Chrome replaces HTTP with SPDY for some Google websites

#6

Post by bemmu » Mon, Aug 08, 2011, 11:37 AM UTC

jannes wrote: post #4

bemmu wrote: post #3

Am I the only one who is constantly getting SPDY protocol errors with Chrome?

What does a SPDY protocol error look like? I don't think I have encountered one yet. Is there any way a user can tell a SPDY and a HTTP error apart?

Here's one I got a minute ago when trying to switch my google docs account.

http://i.imgur.com/9ZMiK.png

I reported the bug. I like that Google is trying to innovate here and will keep using Chrome.

Re: Google Chrome replaces HTTP with SPDY for some Google websites

#7

Post by udp » Mon, Aug 08, 2011, 11:38 AM UTC

I think SPDY is a big step forward, but Chrome only supports it when TLS NPN is used (which requires the server to use a patched version of OpenSSL, and is impossible with SChannel).

If SPDY is to be adopted on a large scale, things like the Connection: Upgrade header should at least be supported as an alternative to NPN.

Re: Google Chrome replaces HTTP with SPDY for some Google websites

#8

Post by mooism2 » Mon, Aug 08, 2011, 11:40 AM UTC

wccrawford wrote: post #2

I Googled but didn't find anything about SPDY with slow or unreliable connections. I wonder if it also speeds that up, or if it might actually make things worse?

Which part of SPDY do you think might make it perform worse than HTTP over slow or unreliable connections? I can think only of TLS, and such SPDY documentation as I have seen claims that the latency drawbacks of using TLS are outweighed by other features of SPDY.

Re: Google Chrome replaces HTTP with SPDY for some Google websites

#9

Post by beaumartinez » Mon, Aug 08, 2011, 11:45 AM UTC

bemmu wrote: post #6

jannes wrote: post #4

Earlier quoted context omitted.

What does a SPDY protocol error look like? I don't think I have encountered one yet. Is there any way a user can tell a SPDY and a HTTP error apart?

Here's one I got a minute ago when trying to switch my google docs account. http://i.imgur.com/9ZMiK.png I reported the bug. I like that Google is trying to innovate here and will keep using Chrome.

Run Wireshark to try and find out what's going on on the wire.

Re: Google Chrome replaces HTTP with SPDY for some Google websites

#10

Post by Kwpolska » Mon, Aug 08, 2011, 11:48 AM UTC

...since 4 months!