v0.7.0.RELEASE
This is the first release of Reactor Netty 0.7, part of Bismuth-RELEASE
Release Train.
This is a recommended update for all Reactor Netty users which fixes a few blockers and some user experience issues.
⚠️ Update considerations and deprecations
- Depending on
Reactor Core
v3.1.0.RELEASE
(see release notes for API changes) - Depending on
Netty
v4.1.15
✨ New features and improvements
- Options and configuration have been reworked
- TCP/HTTP Client and Server expose a copy of the options for information purposes (#66)
- The proxy can be configured to let some hosts bypass it (#125)
- Add
NettyContext
config callback, reworkChannel
config options (#80) - Introduce a step builder for
ClientProxyOptions
(#139) - Expose API for configuring
SslHandler
'scloseNotifyFlushTimeoutMillis
andcloseNotifyReadTimeoutMillis
(b463fc1) - Use the Builder pattern to configure Client/Server and their Options (#120)
- Shutdown and cleanup improvements
- There is now a simple blocking alternative API for client/server that simply need to run from a
main
(#61, #144, #161) - Default configuration changes
- Allow to send files through SSL, expose chunked alternative (#102)
🪲 Bug fixes
- Take
HttpServerOptions#compression(int)
threshold into account (#106) - Make
HttpClient
SSL work on relativeGET
(#109) - Update
pendingResponses
in the event for termination (#89) - Propagate
clientError
/serverError
configurations whenHttpClientRequest#sendWebsocket
is used (#113) - Correctly use base hostname in
HttpClientOptions
even if proxy is configured (#126) - Ensure accept gzip is applied when there is no handler provided (#131)
- Resolve the proxy host and port (#140)
- Make
sendFile
work withZipFileSystem
, useFileChannel
(#146) - Correct handling of pending writes while in parallel completing to send the outbound data. (#134)
- Dispose
ContextHandler
when receive callback signal for cancel (#119) - Emit error signal when the connection is closed prematurely (#138)
- Close before release to avoid acquiring closed connection (723718a)
- Don't send chunked transfer for
DELETE
requests (d44250c) - Create
LoopResources
/PoolResources
only in case the user does not specify their own (336a4c1) - Minor polishes and fixed starving client by http server (cc13744)
- Response codes
204
/205
/304
should specifycontent-length:0
(1f80ca0)