Persist the server config that is received via kSCUP.

net/quic/quic_crypto_client_stream.cc

Index: net/quic/quic_crypto_client_stream.cc
diff --git a/net/quic/quic_crypto_client_stream.cc b/net/quic/quic_crypto_client_stream.cc
index 8c038eff33539a88d0dbd3c6681b5cb10a1ad117..309350ba724cdd8f8f9b0794067afdfbd803aa57 100644
--- a/net/quic/quic_crypto_client_stream.cc
+++ b/net/quic/quic_crypto_client_stream.cc
@@ -158,6 +158,10 @@ void QuicCryptoClientStream::HandleServerConfigUpdateMessage(
         error, "Server config update invalid: " + error_details);
     return;
   }
+  // Persist the new source address token and server config.
+  if (cached->proof_valid()) {

[wtc, 2014/07/31 00:43:06]

If we have access to the proof verifier here, we should verify the proof (for an
https server) that is not yet verified.

[ramant (doing other things), 2014/08/01 19:52:21]

Base on internal CL: 71770356, it looks like  we are not getting certs and proof
when we receive kSCUP message.

Would like to talk to you about async proof verification (may be we could
separate out the state machine for proof verification).

Will hold off checking this change until we merge 71770356. rjshade@: what do
you think? Or is there any advantage to add a TODO for proof verification and
check-in this change for proof's that are already valid.

+    client_session()->OnProofValid(*cached);
+  }
 }
 
 // kMaxClientHellos is the maximum number of times that we'll send a client