Enable session resumption in SSLServerSocketNSS and unit tests

net/socket/ssl_server_socket_nss.cc

Index: net/socket/ssl_server_socket_nss.cc
diff --git a/net/socket/ssl_server_socket_nss.cc b/net/socket/ssl_server_socket_nss.cc
index 270aff085720dee2c9c3385e33f7f3451def0350..283ba50ad058968d746db138011ff3127267cc85 100644
--- a/net/socket/ssl_server_socket_nss.cc
+++ b/net/socket/ssl_server_socket_nss.cc
@@ -292,12 +292,6 @@ int SSLServerSocketNSS::InitializeSSLOptions() {
     return ERR_UNEXPECTED;
   }
 
-  rv = SSL_OptionSet(nss_fd_, SSL_NO_CACHE, PR_TRUE);
-  if (rv != SECSuccess) {
-    LogFailedNSSFunction(net_log_, "SSL_OptionSet", "SSL_NO_CACHE");
-    return ERR_UNEXPECTED;
-  }
-
   rv = SSL_ConfigServerSessionIDCache(1024, 5, 5, NULL);

[wtc, 2011/01/21 21:32:38]

SSL_ConfigServerSessionIDCache should be called only once by
an application.  (It does allow a repeat call though.)

Please add an EnsureNSSSSLServerInit() function, similar to
the EnsureNSSSSLInit() function, to call
SSL_ConfigServerSessionIDCache.

The ssl2_timeout and ssl3_timeout arguments are in seconds.
5 seconds is too short.  I suggest that you pass 0 so that
the default timeout is used (100 seconds for SSL2, 24 hours
for SSL3).

The default max cache entries is 10000, which is too big for
a client application that acts as an SSL server (for peer to
peer).  So passing a smaller value (1024 or even 128) is a
good idea.

   if (rv != SECSuccess) {
     LogFailedNSSFunction(net_log_, "SSL_ConfigureServerSessionIDCache", "");