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 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)

v0.7.12.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)

v0.8.2.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

v0.7.11.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

• Depending on Reactor Core v3.1.11.RELEASE see release notes (fbea1cd)
• Add WebsocketOutbound#sendClose() API (#444, #469)

🪲 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)

v0.8.1.RELEASE

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

This is a recommended update for all Reactor Netty users.

✨ New features and improvements

• Depending on Reactor Core v3.2.1.RELEASE see release notes (c5adcfd)
• Add WARN level log message when TcpResources/UdpResources is updated (#416, #452)

🪲 Bug fixes

• Rename AttributeKey persistent channel to allow coexisting with 0.7 (#440)
• Fix double success (and eager success) in PooledConnectionProvider (#447)
• Do not add PENDING_WRITES to the queue if future is DONE (#445)
• Do not close the channel directly but mark it for closing (#446)
• Ensure Mono from send(receive)Websocket completes when upgrade is confirmed (#393, #456)
• Auto clean global connectionProvider when server on any local address (#90, #449)

📖 Documentation, Tests and Build

• Fix links to new groupId in README badges (#455)

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

@isopov

v0.7.10.RELEASE

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

This is a recommended update for all Reactor Netty users.

✨ New features and improvements

• Depending on Reactor Core v3.1.10.RELEASE see release notes (115cae0)
• Access Logs contents enhancement (#434, #435)
• Add WARN level log message when TcpResources/UdpResources is updated (#416, #452)

🪲 Bug fixes

• Do not add PENDING_WRITES to the queue if future is DONE (#445)
• Do not close the channel directly but mark it for closing (#446)
• Defer decision for DefaultFileRegion vs ChunkedInput (#430, #451)
• Ensure Mono from send(receive)Websocket completes when upgrade is confirmed (#393, #456)

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

@blackwizard1812

v0.7.9.RELEASE

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

This is a recommended update for all Reactor Netty users.

✨ New features and improvements

• Depending on Reactor Core v3.1.9.RELEASE see release notes (ce52656)
• Depending on Netty v4.1.29 (3002cdc)
• Prepend channel ID in all possible logging (#33)
• Add Http Server Access Log (#301, #428)

🪲 Bug fixes

• Release the incoming message on the server when the decoding failed (#406, #409)
• Release the incoming message on the client when the decoding failed (#406, #417)
• Apply compression predicate before sendFile invocation (#411, #415)
• When it is the last drained element do not schedule the flush operation (#419)
• Track active/inactive connections in the pool (#420)

📖 Documentation, Tests and Build

• Update Gradle version to 4.8.1 (20e1c54)

v0.7.8.RELEASE

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

This is a recommended update for all Reactor Netty users.

✨ New features and improvements

• Depending on Reactor Core v3.1.8.RELEASE see release notes (43409bb)
• Depending on Netty v4.1.25 (#356)

🪲 Bug fixes

• Ensure completion event is sent for HttpClientWSOperations#onClose (#345 #346)
• Suppress unchecked warnings in DefaultLoopResources#disposeLater method (#347)
• Add the missing @Override (#350)
• Use Objects#equals for HttpMethod and HttpResponseStatus comparison (#350)
• Use grouping parenthesis to make the operator precedence explicit (#350)
• Improved ws condition support (#354)
• Add options and head to HttpServerRoutes (#363)
• Force channel close, when an error happens while sending the request body, but the headers were sent already (#361 #371)

📖 Documentation, Tests and Build

• Fix warning in asciidoc rendering (#347)
• Fix unchecked warnings in tests (#347)
• Enable rawtypes linting and resolve or suppress warnings (#347)
• Improve asciidoctor configuration in build (#348)
• Enable errorprone compiler plugin (#349)
• Express the duration time more clear in the tests (#350)
• Explicitly specify the charset that will be used (#350)
• Use StringBuilder instead of String Buffer (#350)
• Make the inner class static (#350)
• Log the exception instead of calling printStackTrace (#350)

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

@lhotari, @lerouxrgd, @segabriel

v0.7.7.RELEASE

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

This is a recommended update for all Reactor Netty users.

✨ New features and improvements

• Depending on Reactor Core v3.1.7.RELEASE see release notes (1561042)
• Depending on Netty v4.1.24 (#328)
• Change the dependency to netty-transport-native-epoll to the one with linux-x86_64 classifier (#329, #338)

🪲 Bug fixes

• Do not share pipeline state in fields of the FileChunkedStrategy instance (#319)
• Add handling of offset and length to FileChunkedStrategy (#320)
• Handle the delayed writes when onComplete/onError event is sent (#321, #326)
• Take in account the delayed writes when calculating the requested
  and produced items when onComplete/onError event is sent. (#316, #327)
• Fix log messages (#336)
• Ensure CloseWebSocketFrame will be sent by the Server/Client (#332, #334)
• Forward user-facing cancel to send(Publisher) cancel (#317, #335)
• Remove the additional logging when the error is propagated (#339)
• When received the last HTTP packet but still sending the request, force the channel close (#323, #342, #343, #177)
• ChannelOperations#isDisposed should check for channel active (51b33c3)
• When compression is enabled do not send file with zero copy instead
  use chunking (#340, #341)

📖 Documentation, Tests and Build

• Fix minor inconsistency in javadoc (#318)
• Update Gradle version to 4.6 (65b29d7)
• Refactor http send file tests to also run with SSL (#320)
• Update javadoc overview (#325)
• Test websocket connection alive when transformation errors (23bd118)

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

@lhotari, @sdeleuze

v0.7.6.RELEASE

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

This is a recommended update for all Reactor Netty users.

✨ New features and improvements

• Depending on Reactor Core v3.1.6.RELEASE see release notes (10ae803)
• Add Reactor Core v3.1.6.RELEASE non blocking thread marker support (#312, #314)

🪲 Bug fixes

• Ensure StackOverflowError is not thrown on the client when sending the request body as a byte array (#303, #304)
• When the request decoding failed with TooLongFrameException on the server, 413 Request Entity Too Large will be returned otherwise 400 Bad Request (#309, #310)