Defines SSLServerSocket and implements SSLServerSocketNSS

net/base/ssl_config_service.h

Index: net/base/ssl_config_service.h
diff --git a/net/base/ssl_config_service.h b/net/base/ssl_config_service.h
index 0f796564fb306f90338c893441700b70decc85f7..e9aba051e8e3fb02460d5f67e49f82425602fe18 100644
--- a/net/base/ssl_config_service.h
+++ b/net/base/ssl_config_service.h
@@ -31,6 +31,7 @@ struct SSLConfig {
   bool snap_start_enabled;  // True if we'll try Snap Start handshakes.
   // True if we'll do async checks for certificate provenance using DNS.
   bool dns_cert_provenance_checking_enabled;
+  bool no_cache_enabled;  // Disable caching.

[wtc, 2010/12/17 00:16:26]

no_cache_enabled => session_cache_disabled

More important, we should avoid adding this config setting
if we can.  Can we use a small SSL session cache for
SSLServerSocket?

[Alpha Left Google, 2010/12/17 08:30:43]

I'd like to simply the implementations in the first version. What about adding a
TODO and file a bug to complete this feature?

[wtc, 2010/12/17 16:38:32]

Adding a TODO for enabling server session cache is fine.

But you should not need to disable client session cache.
Why do you need to do that in SSLServerSocketTest?

[Alpha Left Google, 2010/12/17 20:09:57]

SSLClientSocketNSS uses session key between tests. Since server implementation
doesn't support session key, tests after the one will fail since it fails
handshaking.

 
   // Cipher suites which should be explicitly prevented from being used. By
   // default, all cipher suites supported by the underlying SSL implementation