Enable session resumption in SSLServerSocketNSS and unit tests

Enable session resumption in SSLServerSocketNSS and unit tests

SSL_ConfigServerSessionIDCache() is being used in SSLServerSocketNSS and
enabling session resumption since passes are now passing.

BUG=67236
TEST=net_unittests, remoting_unittests

Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=72186

[Alpha Left Google, 2011-01-20 06:14:32]

I haven't tested SSLServerSocketTest after I added the usage of
SSL_ConfigServerSessionIDCache() and now the tests are passing so removing the
code path for disable session resumption.

[Alpha Left Google, 2011-01-21 18:57:49]

ping.

[wtc, 2011-01-21 20:05:35]

LGTM.  I will write to you later about a problem with the
way you call SSL_ConfigServerSessionIDCache.

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

http://codereview.chromium.org/6370008/diff/1/net/socket/ssl_server_socket_ns...
File net/socket/ssl_server_socket_nss.cc (right):

http://codereview.chromium.org/6370008/diff/1/net/socket/ssl_server_socket_ns...
net/socket/ssl_server_socket_nss.cc:295: rv =
SSL_ConfigServerSessionIDCache(1024, 5, 5, NULL);
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.