> 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.
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.