Michael Bildner 58dc7f7902 Do not bother closing SSL enging inbound if the outbound has already been closed. ... Motivation: Invoking the javax.net.ssl.SSLEngine.closeInbound() method will send a fatal alert and invalidate the SSL session if a close_notify alert has not been received. From the javadoc: If the application initiated the closing process by calling closeOutbound(), under some circumstances it is not required that the initiator wait for the peer's corresponding close message. (See section 7.2.1 of the TLS specification (RFC 2246) for more information on waiting for closure alerts.) In such cases, this method need not be called. Always invoking the closeInbound() method without regard to whether or not the closeOutbound() method has been invoked could lead to invalidating perfectly valid SSL sessions. Modifications: Added an instance variable to track whether the SSLEngine.closeOutbound() method has been invoked. When the instance variable is true, the SSLEngine.closeInbound() method doesn't need to be invoked. Result: SSL sessions will not be invalidated if the outbound side has been closed but a close_notify alert hasn't been received.		2015-09-06 10:00:46 +02:00
..
src/main/java/io/netty/testsuite	Do not bother closing SSL enging inbound if the outbound has already been closed.	2015-09-06 10:00:46 +02:00
.gitignore	updated udt and connection test	2013-05-14 06:46:07 +02:00
pom.xml	[maven-release-plugin] prepare for next development iteration	2015-09-02 11:45:20 +02:00