QUIC - track CHLO's reject reason for secure QUIC vs insecure QUIC.

net/quic/crypto/quic_crypto_client_config.h

Index: net/quic/crypto/quic_crypto_client_config.h
diff --git a/net/quic/crypto/quic_crypto_client_config.h b/net/quic/crypto/quic_crypto_client_config.h
index 131e6da4fe119229760279c6e4c8398c757193b6..88be04daf4a35031d9245f4ab1a3cc431b1ad606 100644
--- a/net/quic/crypto/quic_crypto_client_config.h
+++ b/net/quic/crypto/quic_crypto_client_config.h
@@ -186,10 +186,12 @@ class NET_EXPORT_PRIVATE QuicCryptoClientConfig : public QuicCryptoConfig {
   // true for that server's CachedState. If the rejection message contains
   // state about a future handshake (i.e. an nonce value from the server), then
   // it will be saved in |out_params|. |now| is used to judge whether the
-  // server config in the rejection message has expired.
+  // server config in the rejection message has expired. |is_https| is used to
+  // track reject reason for secure vs insecure QUIC.
   QuicErrorCode ProcessRejection(const CryptoHandshakeMessage& rej,
                                  QuicWallTime now,
                                  CachedState* cached,
+                                 bool is_https,

[ramant (doing other things), 2014/07/25 02:49:06]

Should we check if rej has kCertificateTag or not instead of passing is_https as
argument from server_id_.is_https()?

                                  QuicCryptoNegotiatedParameters* out_params,
                                  std::string* error_details);