Skip to content

@violetagg violetagg released this Mar 26, 2019 · 126 commits to master since this release

This is the 7th release of Reactor Netty 0.8, part of Californium-SR6 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.8.RELEASE, see release notes (#603)
  • Updated Netty version to 4.1.34.Final (#628)
  • Deprecate HttpClient#chunkedTransfer (#553)

🐞 Bug fixes

  • Update PooledConnectionProvider.Pool#inactiveConnections when channel closed (ef4b60c)
  • Do not send Transfer-Encoding when there is Content-Length (#614, #616)
  • Ensure the logging for RedirectClientException is with DEBUG level (#618)
  • Handle correctly the Connection header with a comma separated list as value (#621, #632, #634)
  • Update parseAddress behavior to handle ipv6 addresses without bracket notation and add parseAddress tests to verify (#625, #626)
  • Fix possible memory leak when channel inactive event is sent on the server and the transport is native (#630, #631)
  • Handle IllegalReferenceCountException when a cancel signal is received to ByteBufFlux#aggregate (#636, #637)
  • When obtaining the ConnectionObserver remove the Bootstrap option only if it exists (b133b78)
  • Do not release the channel twice (#665)
  • Ensure context is available when HttpClient#doAfterResponse (#651, #664)

📖 Documentation, Tests and Build

  • Fix HttpServer javadoc (#623)

👍 Thanks to the following contributors that also participated to this release

@flyinprogrammer, @gasches, @RayJSeth, @dave-fl, Spring community (gateway, framework) and the many realtime reports from our Gitter channel !

Assets 2

@violetagg violetagg released this Mar 26, 2019 · 2 commits to 0.7.x since this release

This is the 16th release of Reactor Netty 0.7, part of Bismuth-SR17 Release Train.

This is a recommended update for all Reactor Netty 0.7.x users.

New features and improvements

  • Depending on Reactor Core v3.1.16.RELEASE see release notes (db1e290)
  • Updated Netty version to 4.1.34.Final (#628)
  • Switch the connection pool to use the oldest Channel (#601)

🐞 Bug fixes

  • Fix sending an explicit empty body for GET and HEAD when using SSL (#576)
  • Fix possible memory leak when channel inactive event is sent on the server and the transport is native (#630, #631)
  • Handle correctly the Connection header with a comma separated list as value (#632, #634)
  • Handle IllegalReferenceCountException when a cancel signal is received to ByteBufFlux#aggregate (#636, #637)
Assets 2

@violetagg violetagg released this Feb 12, 2019 · 172 commits to master since this release

This is the 6th release of Reactor Netty 0.8, part of Californium-SR5 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.6.RELEASE, see release notes (a736d9c)
  • Updated Netty version to 4.1.33.Final (2b17d8c)
  • Make PrematureCloseException public (#591, #593)
  • Switch the connection pool to use the oldest Channel (#601, #602)
  • By default the server will listen on any local address (#604)

🐞 Bug fixes

  • Correctly calculate address and password when ProxyProvider#equals/#hashcode is called (#567, #566)
  • Fix sending an explicit empty body for GET and HEAD when using SSL (#575, #576)
  • Log with level DEBUG, the Connection reset by peer when there is no ChannelOperations (#579)
  • Correctly wrap BindException when a native transport is in use (epoll / kqueue) (#583)
  • HttpClient will retry the request only once when Connection reset by peer occurs (#587, #588)
  • When the connection observes an error, log the Exception with level WARN as it is propagated (#582, #590, #592)
  • Ensure the message is released when the I/O handler throws RuntimeException (#595, #596)
  • Add doOnDiscard in order to handle cancel/error scenarios, when sending a body for GET and HEAD (#598, #599)
  • Ensure the fixed ConnectionProvider uses all configured threads (#600, #607)
  • Ensure HttpClientRequest / HttpClientResponse#redirectedFrom returns the correct number of the redirections (#606, #608)
  • Switch from Exceptions#throwIfFatal to Exceptions#throwIfJvmFatal (#609)
  • When IOException happens on the server while reading/writing treat it as a client side error. Log level will be DEBUG instead of ERROR (#555, #610)

👍 Thanks to the following contributors that also participated to this release

@fred84, @dave-fl, Spring community (gateway, framework) and the many realtime reports from our Gitter channel !

Assets 2

@violetagg violetagg released this Jan 9, 2019 · 203 commits to master since this release

This is the 5th release of Reactor Netty 0.8, part of Californium-SR4 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.5.RELEASE see release notes (9157c5a)
  • Updated Netty version to 4.1.32.Final (3fd520e)
  • Introduce a new HttpServer state REQUEST_RECEIVED (b52974c)
  • New HttpClient API to allow configuring redirects via a predicate (#522, #543)
  • HttpServer/Client: Support WebSocket compression handler (#507, #545)

🐞 Bug fixes

  • Ensure all channelRead events are propagated to the handlers that are added with TcpServer#doOnConnection (#525, #526)
  • Ensure nonProxyHost configuration is applied when only uri is supplied (#523, #527)
  • Fix HttpClientFinalizer cleanup for interrupted responses (#529, #530)
  • Log with level ERROR only the errors observed by the connection that will not be retried (#534, #535)
  • When the connection is closed, stop publishing data (#536)
  • Do not add Transfer-Encoding when Content-Length is available from request headers (#548, #550)
  • Attach a callback to react on client cancellation (#551)
  • Ensure the object scheduled for writing is released, when Content-Length: 0. Ensure the cancellation signal is propagated to the Publisher, scheduled for writing, when Content-Length: 0 and Connection: close (#554)
  • Support X-Forwarded-Host AND X-Forwarded-For (#563)
  • Use ByteBuf#(write|read)CharSequence when transforming from/to String (#557)

📖 Documentation, Tests and Build

  • Updated Gradle version to 4.10.2 (91ba02c)
  • Update README.md (#552)

👍 Thanks to the following contributors that also participated to this release

@trecloux

Assets 2

@simonbasle simonbasle released this Jan 9, 2019 · 517 commits to master since this release

This is the 15th release of Reactor Netty 0.7, part of Bismuth-SR15 Release Train.

This is a recommended update for all Reactor Netty 0.7.x users.

This release contains all the elements from 0.7.13.RELEASE but depends on Reactor Core v3.1.14.RELEASE, because the previous version had a build problem. This fixup release is intended as a way to avoid users mistakenly pulling in 3.1.13 (eg. when not using the BOM).

New features and improvements

🐞 Bug fixes

  • When the connection is closed, stop publishing data (#536)
  • Ensure the object scheduled for writing is released, when Content-Length: 0. Ensure the cancellation signal is propagated to the Publisher, scheduled for writing, when Content-Length: 0 and Connection: close (#554)

📖 Documentation, Tests and Build

  • Updated Gradle version to 4.10.2 (26f97df)
Assets 2

@violetagg violetagg released this Jan 8, 2019 · 23 commits to 0.7.x since this release

⚠️ Don't use this release in a standalone way, or manually bump reactor-core to 3.1.14.RELEASE (see https://github.com/reactor/reactor-netty/releases/tag/v0.7.14.RELEASE)

This is the 14th release of Reactor Netty 0.7. It is superseded by 0.7.14 in the Bismuth-SR15 release train.

New features and improvements

🐞 Bug fixes

  • When the connection is closed, stop publishing data (#536)
  • Ensure the object scheduled for writing is released, when Content-Length: 0. Ensure the cancellation signal is propagated to the Publisher, scheduled for writing, when Content-Length: 0 and Connection: close (#554)

📖 Documentation, Tests and Build

  • Updated Gradle version to 4.10.2 (26f97df)
Assets 2

@simonbasle simonbasle released this Nov 23, 2018 · 255 commits to master since this 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 to DEBUG when creating TcpResources/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) for GET/HEAD: mark content length; do not use direct memory to avoid leak (#514, #516)
  • 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 use SslProvider.OPENSSL when OpenSSL#isAvailable (#491, #496)

📖 Documentation, Tests and Build

  • Test for HttpClient using Proxy configuration (#129, #502)
  • Fixed memory leaks in tests (cb6d1ad)
Assets 2

@simonbasle simonbasle released this Nov 22, 2018 · 537 commits to master since this release

This is the 13th release of Reactor Netty 0.7, part of Bismuth-SR14 Release Train.

This is a recommended update for all Reactor Netty 0.7.x users.

New features and improvements

  • Depending on Reactor Core v3.1.12.RELEASE see release notes (e34bbef)
  • Updated Netty version to 4.1.31.Final (dbb79bf)
  • Changed log level from WARN to DEBUG when creating TcpResources/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) for GET/HEAD: mark content length; do not use direct memory to avoid leak (#514, #516)
  • 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)

📖 Documentation, Tests and Build

  • Test for HttpClient using Proxy configuration (#129, #502)
  • Fixed memory leaks in tests (cb6d1ad)
Assets 2

@violetagg violetagg released this Oct 30, 2018 · 313 commits to master since this release

This is the 3nd release of Reactor Netty 0.8, part of Californium-SR2 Release Train.

This is a recommended update for all Reactor Netty users.

New features and improvements

  • Depending on Reactor Core v3.2.2.RELEASE see release notes (d6c3a6e)
  • Add TcpClient(Server)#secure(SslProvider) and deprecate TcpClientServer()#secure(SslContext) in favour of TcpClientServer()#secure(Consumer) (ac7186a)
  • Add wiretap(boolean) for the server and client configuration and deprecate wiretap() (#479)
  • Add HttpClientRequest/HttpClientResponse#currentContext() (#485)
  • Add HttpClient doOnError, doOnRequestError and doOnResponseError (#486)
  • Add HttpClient#mapConnect, a low level connection interceptor (33e1a84)

🐞 Bug fixes

  • Fix extra character trimming if baseUrl ends with a slash (#461)
  • Generate correct HOST header when IPv6 with scope_id (#462)
  • Ensure errors while upgrading to websocket will be propagated (#460, #463)
  • Ensure no Transfer-Encoding/Content-Length will be sent when response code is 304 (Not Modified) (#465, #467)
  • Handle IllegalReferenceCountException in ByteBuf(Flux|Mono)#as... methods (#470)
  • Ensure WebsocketOutbound#sendClose() will cancel any previous send operation and will send a close frame on subscribe then close the underlying channel. (#444, #469)
  • Ensure lazy remote address is converted before finalizing pipeline handlers (#473, #475)
  • Put more information into the key for pooled connections (#407, #450)
  • Application Protocol is not enabled by HttpServer#secure (#484)

📖 Documentation, Tests and Build

  • Fixed WebsocketTest#duplexEcho failure on Windows OS (#459)

👍 Thanks to the following contributors that also participated to this release

@vooft

Assets 2

@violetagg violetagg released this Oct 27, 2018 · 61 commits to 0.7.x since this release

This is the 12th release of Reactor Netty 0.7, part of Bismuth-SR13 Release Train.

This is a recommended update for all Reactor Netty users.

New features and improvements

🐞 Bug fixes

  • Ensure no Transfer-Encoding/Content-Length will be sent when response code is 304 (Not Modified) (#465, #467)
  • Ensure the pipeline is cleaned after sending a chunked file (#468)
  • Avoid NPE when a connect address isn't specified and HttpClient#newHandler is in use (#474)
  • Handle IllegalReferenceCountException in ByteBuf(Flux|Mono)#as... methods (#470)
  • Fix Out of Order handling with pool acquisition (#388, #413, #482, #483)
  • Strips query parameters from template matching (#30, #433)
Assets 2
You can’t perform that action at this time.