net: don't remember TLS intolerant servers.

net/test/base_test_server.h

Index: net/test/base_test_server.h
diff --git a/net/test/base_test_server.h b/net/test/base_test_server.h
index fd04e55133b7e83bf860849b70e2c9ba00c419d0..9624ac4474d68de1e1e1b5244615836e32864aef 100644
--- a/net/test/base_test_server.h
+++ b/net/test/base_test_server.h
@@ -126,6 +126,10 @@ class BaseTestServer {
     // causes it to log session cache actions and echo the log on
     // /ssl-session-cache.
     bool record_resume;
+
+    // If true, the server will abruptly close any TLS connections in order to
+    // test SSLv3 fallback.

[wtc, 2012/04/26 00:49:14]

COMMENT BUG: I was confused by this comment because I thought
by "abrutly closing a TLS connection" you meant closing the
underlying TCP connection, which is one behavior of TLS-intolerant
servers.

How about "the server will abort a TLS handshake with a handshake_failure alert"
or just "the server will abort any TLS handshakes"?

Please make the same change to the comments in the Python files.

[agl, 2012/04/26 17:03:29]

Done.

+    bool tls_intolerant;
   };
 
   // Pass as the 'host' parameter during construction to server on 127.0.0.1