v0.9.10.RELEASE
·
265 commits
to 0.9.x
since this release
❗ This release contains a regression - in some cases Reactor Netty hangs when reading the incoming data, v0.9.14.RELEASE
was released with a fix addressing this issue. Prefer using the later.
Reactor Netty
0.9.10.RELEASE
is part of Dysprosium-SR10
Release Train.
This is a recommended update for all Reactor Netty 0.9.x
users.
See also release notes from 0.8.20 for changes that were inherited from the 0.8.x maintenance release.
⚠️ Update considerations and deprecations
- Deprecate
(Tcp|Udp)Client/Server#bootstrap
method in favour of methods exposed on client/server level. (#1175)
✨ New features and improvements
- Depends on
Reactor Core
v3.3.8.RELEASE
, see release notes (cc37976) - Request headers are available now from both
HttpClientRequest
andHttpClientResponse
. (#1031, #1192) ProxyProvider
changes:
🪲 Bug fixes
- Enhance internal implementation taking into account no concurrency in
eventLoop
. (#503, #1185) - Ensure change to the state
CONFIGURED
is done after notifying that the connection is acquired successfully. Cancel the subscription when disposingChannelOperations
(#1165, #1198) - Fix memory leaks when send operation races with cancellation signal. (#1172, #1208, #1211)
- Ensure that the custom status code phrase is preserved when creating a
FullHttpResponse
. (#1180, #1181) - Retry the request once if the connection was closed before sending the actual request. (#1183)
- Fix
HttpClientOperations
so that it doesn't offloadonSubscribe(subscription)
. (#1189) - Revert
Use resourceUrl for resolving the websocketUrl (#1047)
. (#1194) - Use log level
DEBUG
forConnection reset by peer
post termination inbound exception. (#1203)