News for hackers. Stuff that matters.
Re:QUIC – Next-generation multiplex transport over UDP by crazygringo on Wednesday February 12, 2014 @07:13PM (#7228452)
Wait, so how do I enable it on Chrome? I've gone to:

chrome://net-internals/#quic

like the slide says, but Chrome just says "QUIC Enabled: false" without any switch to turn it on. (Chrome 32 on OSX.)

Edit: turns out the answer is to go to chrome://flags/#enable-quic

Also, what web servers support QUIC? Is there some kind of Apache add-on in development? And how will Chrome know whether to try to connect via QUIC or not? If QUIC gets enabled in my Chrome, does this mean Chrome tries to establish both a QUIC and TCP connection to each server always?

Re:QUIC – Next-generation multiplex transport over UDP by rjshade on Wednesday February 12, 2014 @07:34PM (#7228541)
> And how will Chrome know whether to try to connect via QUIC or not?

Chrome looks for the "alternate-protocol:443:quic" response header (in non-QUIC requests). Once it sees this it will attempt to talk QUIC in future requests to the same domain.

And thanks for pointing out the omission of chrome://flags/#enable-quic in the slides. Have fixed this.

Re:QUIC – Next-generation multiplex transport over UDP by loganfsmyth on Wednesday February 12, 2014 @09:34PM (#7228968)
The protocol is still in prototype development, so there is no general server support yet. At least some of Google's severs have it enabled though.
Re:QUIC – Next-generation multiplex transport over UDP by virtue3 on Wednesday February 12, 2014 @07:16PM (#7228469)