Actually enable Alternate-Protocol support for QUIC.

net/http/http_stream_factory.cc

Index: net/http/http_stream_factory.cc
diff --git a/net/http/http_stream_factory.cc b/net/http/http_stream_factory.cc
index a48fcb6cd1ff2b1a783e7a8c5951e5b1245562ee..2aad5127b9ca5735ada098a7c0cd78f9c0eee0f3 100644
--- a/net/http/http_stream_factory.cc
+++ b/net/http/http_stream_factory.cc
@@ -144,6 +144,7 @@ void HttpStreamFactory::EnableNpnSpdy() {
   std::vector<std::string> next_protos;
   next_protos.push_back("http/1.1");
   next_protos.push_back("spdy/2");
+  next_protos.push_back("quic");

[willchan no longer on Chromium, 2013/06/20 17:48:08]

Does order matter? Historically order matters for this vector. But you guys
aren't actually sending this within NPN are you? I'm not understanding how this
is supposed to work.

[Ryan Hamilton, 2013/06/20 17:56:47]

I don't think that order matters.  If you notice, each of these methods calls
SetNextProtos, which simply iterates over the list and sets
enabled_protocols_[foo] = true.  As you say, we're not sending QUIC via NPN, but
rather Alternate-Protocol.  These "EnableFoo" methods which end up setting
enabled_protocols_ configure both of these mechanism.  Since we use
Alternate-Protocol, this works fine.  That being said, I re-ordered this list to
match the others (sorted alphabetically).

   SetNextProtos(next_protos);
 }
 
@@ -163,6 +164,7 @@ void HttpStreamFactory::EnableNpnSpdy3() {
   set_use_alternate_protocols(true);
   std::vector<std::string> next_protos;
   next_protos.push_back("http/1.1");
+  next_protos.push_back("quic");
   next_protos.push_back("spdy/2");
   next_protos.push_back("spdy/3");
   SetNextProtos(next_protos);
@@ -173,6 +175,7 @@ void HttpStreamFactory::EnableNpnSpdy31() {
   set_use_alternate_protocols(true);
   std::vector<std::string> next_protos;
   next_protos.push_back("http/1.1");
+  next_protos.push_back("quic");
   next_protos.push_back("spdy/2");
   next_protos.push_back("spdy/3");
   next_protos.push_back("spdy/3.1");