To mitigate the effects of hanging 0-RTT QUIC connections,
set up a timer to cancel any requests, if the handshake takes too long.
The requests will be retried and will use either QUIC or TCP, whichever
connects first.
Review URL: https://codereview.chromium.org/318993004
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@275552 0039d316-1c4b-4281-b951-d872f2087c98
diff --git a/net/quic/quic_client_session_test.cc b/net/quic/quic_client_session_test.cc
index 2ca8bc9..8706d7c 100644
--- a/net/quic/quic_client_session_test.cc
+++ b/net/quic/quic_client_session_test.cc
@@ -73,7 +73,9 @@
QuicServerId(kServerHostname, kServerPort, false,
PRIVACY_MODE_DISABLED),
DefaultQuicConfig(), kInitialFlowControlWindowForTest,
- &crypto_config_, &net_log_) {
+ &crypto_config_,
+ base::MessageLoop::current()->message_loop_proxy().get(),
+ &net_log_) {
session_.config()->SetDefaults();
crypto_config_.SetDefaults();
}
