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)

v0.7.5.RELEASE

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

This is a recommended update for all Reactor Netty users.

✨ New features and improvements

• Depending on Reactor Core v3.1.5.RELEASE see release notes (90390d7)
• Depending on Netty v4.1.22 (cc44e71)
• Support expect 100-continue (#293, #295)
• HttpServerBuilder now exposes a compression(BiPredicate<Req,Res>).
  The predicate is evaluated before committing response header/status.
  If the predicate is true, compression is enabled for the given response.
  The minimum compression threshold now uses content-length predicate. (#218, #292, #298, #299)

🪲 Bug fixes

• Set the channel closeFuture to release to the pool only once and if a Channel was successfully acquired (#289, #290)
• Fix Context transferring for implicitly connected streams (#288)
• Polish when to mark an HTTP connection persistent (85e5614)
• Refinements related to http request/response lifecycle (95b22e0)
• Optimize scalar map transformations and polish PublisherContext (4960c0f)

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

@OlegDokuka

v0.7.4.RELEASE

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

This is a recommended update for all Reactor Netty users.

✨ New features and improvements

• Depending on Reactor Core v3.1.4.RELEASE see release notes (d22208f)
• Depending on Netty v4.1.21 (6e73dfe)

🪲 Bug fixes

• Fixed IllegalArgumentException: Channel [...] was not acquired from this ChannelPool (#266, #280)
• On channelInactive event, do not fire error when the inbound has been already cancelled/disposed (#267, #281)
• Ensure server will send a response in case websocket upgrade failure (#268, #269)
• On inbound cancelled event do not close the connection if the inbound's been disposed (d8e9ca1)
• When HttpClient receives AbortedException/IOException, it will retry once
  and then will return the exception so that the user can decide how many
  retries to do and with what delay (#257, #270, #272)
• Enable hostname verification in client SSL config (#222, #275)
• Extended key for the connection pool cache (#276)
• Resolve the relative location when redirecting (#278, #279)
• Connection close should always be bridged to pool release (#285, #286)
• Fix a possible reference count leak for empty WS client upgrade body (101) (b6adfec, 9dfc8e4)
• Ensure ChannelPromise objects are updated when filtering the messages (#282, #287)

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

@bclozel, @hananaharonof

v0.7.3.RELEASE

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

This is a recommended update for all Reactor Netty users.

✨ New features and improvements

• Depending on Reactor Core v3.1.3.RELEASE see release notes (b37a31b)
• Depending on Netty v4.1.20 (877d852)
• Depending on Reactive Streams 1.0.2 (7249011)
• Add support for KQueue (#212)
• Expose Netty HttpServerCodec options in HttpServer (#150)

🪲 Bug fixes

• Emit error signal when the connection is closed prematurely (#224)
• Remove the special handling of status code 205 (#216)
• When the writing Publisher completes with an error, ensure the error signal is propagated to the subscriber. (#231)
• Fixed a race issue in HttpServerOperations#onOutboundComplete (17ada56)
• On outbound error HttpServer will not send EmptyLastContent, but will close the connection (#239)
• Ensure HttpClient will emit an error when connection is closed from the server side (#237)
• Ensure write chunks are always in a correct order (#232)
• Ensure code 301 can be controlled by HttpClientRequest#followRedirect (#253)
• HttpServer outbound complete refinements (#264, #248)
  • Try detecting outbound complete with autoRead only if non keep alive
  • Leave HttpServerOperations#onOutboundComplete to take precedence for the terminal event
  • Clear ChannelOperations before writing the response
  • Try deferring for all flow the state cleaning inside handler
  • Fix HttpServerHandler#shouldKeepAlive

v0.7.2.RELEASE

This is the third release of Reactor Netty 0.7, part of Bismuth-SR4 Release Train.

This is a recommended update for all Reactor Netty users.

✨ New features and improvements

• Depending on Reactor Core v3.1.2.RELEASE see release notes (3b6fa6a)
• Depending on Netty v4.1.17 (73b7945)
• Introduce flush on each with event loop option (#203)

🪲 Bug fixes

• Omit filling stack trace for RedirectClientException (#193)
• Fix possible ByteBuf leaks (f7a2df4)
• Create default UDP LoopResource on demand (#192)
• Tweak FluxReceive and reduce preemptive read on server (#194)
• Correct exception message in case selector threads number is not positive (#200)
• Prefer ReferenceCountUtil#release instead of ReferenceCountUtil#safeRelease (#201)
• Improve OSGI Import-Package (#209)
• Improvements in a flush implementation (#206, #207, 8c19d46)
• Handle DatagramChannel in NettyContext#address (#210)
• Premature response commit drops last request http packet (#213)
• ByteBufFlux#fromPath: Release the buffer only on completion or on error (#215)

📖 Documentation, Tests and Build

• Fixed javadoc (#190, #191, #197, 9897a7c)
• Fix test builder when DNS resolving (f600a9c)
• Fix timeout in a test (f34911c)
• Clear some memory leaks in tests (0e2ff98)
• Fix encoding problems in javadoc when using Java 8 (507d29d)

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

@akiraly, @lhotari, @janvdbergh

v0.7.1.RELEASE

This is the second release of Reactor-Netty 0.7, part of Bismuth-SR3 Release Train.

This is a recommended update for all Reactor Netty users.

✨ New features and improvements

• Use HttpClientCodec/HttpServerCodec (cce4d57)
• Increase the default timeout, introduce a new method with timeout (#179)
• Separate UdpClient/UdpServer (#137)

🪲 Bug fixes

• Fixed a memory leak with keep-alive connections (#176, 21fd7a9)
• Prevent unwanted reverse DNS lookup calls (1bf036a)
• Leave connection gracefully finishes on http 40x, 50x, 301/302 (9eb3a10)
• Fix possible ByteBuf leaks (f1d8576)
• Release buffers at fromPath level (6269251, f34df23)
• Drop out of sequence http client frames when server close (#186)
• Remove the special handling of status codes 204/304 (116466f)
• Do not replace the HttpServerCodec (ea736c5)
• Do not set content length when HEAD request (#171)

📖 Documentation, Tests and Build

• Migrate to Gradle 4.2 (50196f3)

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

@lhotari