Yannick Koehler wrote:
> And what are the reason for Mozilla to re-negotiate new session ID?
It appears that the cause of this bug has been found and fixed.
The bug was in the IPv6 emulation code in NSPR.
It caused the wrong IP addresses and port numbers to be given to SSL when
SSL asked the question "what are the IP address and port number of the
server to which this socket is connected?", thereby making it impossible
for SSL to find previously used SSL sessions in its store of old SSL sessions.
Now that the correct addresses are being reported to SSL, SSL session restart
should work as expected.
--
Nelson Bolyard Sun / Netscape Alliance
Disclaimer: I speak for myself, not for Netscape
