v0.8.3.RELEASE
This is the 4th release of Reactor Netty
0.8
, part of Californium-SR3
Release Train.
This is a recommended update for all Reactor Netty 0.8.x
users.
✨ New features and improvements
- Depending on
Reactor Core
v3.2.3.RELEASE
see release notes (6ed883d) - Updated Netty version to
4.1.31.Final
(dbb79bf) - Changed log level from
WARN
toDEBUG
when creatingTcpResources
/UdpResources
(#487, #510) - Lazy initialisation for
NIO
server/client loops (#499)
🪲 Bug fixes
- Context is now propagated to websocket handler and client handler (#488, #489)
- Ensure server and client will share the loop resources when native transport (#505)
- When creating client loop resources do not invoke shutdown on the
ColocatedEventLoopGroup
(#511) - Eliminate potential sources of
ByteBuf
leaks:- Do not invoke
ByteBuf.retain
as the bytes are copied to the new buffer (#512) - When close websocket event has been already sent, release the incoming
CloseWebSocketFrame
(#513) - When redirecting ensure the
HttpResponse
is released (#515) - Improve
HttpClient#send(Publisher)
forGET
/HEAD
: mark content length; do not use direct memory to avoid leak (#514, #516)
- Do not invoke
- If the channel is not active do not continue with writing (#508, #509)
- Revert "When it is the last drained element do not schedule the flush operation" (#506)
- When writing full message mark the body as sent (#519)
- Ensure
HOST
header is the real remote address not the proxy one (#490, #500) - Default
TCP
configuration will useSslProvider.OPENSSL
whenOpenSSL#isAvailable
(#491, #496)