Scott Mitchell 8c5eeb581e SslHandler promise completion incorrect if write doesn't immediately ... complete Motivation: SslHandler removes a Buffer/Promise pair from AbstractCoalescingBufferQueue when wrapping data. However it is possible the SSLEngine will not consume the entire buffer. In this case SslHandler adds the Buffer back to the queue, but doesn't add the Promise back to the queue. This may result in the promise completing immediately in finishFlush, and generally not correlating to the completion of writing the corresponding Buffer Modifications: - AbstractCoalescingBufferQueue#addFirst should also support adding the ChannelPromise - In the event of a handshake timeout we should immediately fail pending writes immediately to get a more accurate exception Result: Fixes https://github.com/netty/netty/issues/7378.		2017-11-07 09:24:40 -08:00
..
java/io/netty/handler	SslHandler promise completion incorrect if write doesn't immediately	2017-11-07 09:24:40 -08:00
resources/io/netty/handler/ssl	OpenSslEngine should respect hostname verification	2017-02-17 13:21:29 -08:00