Skip navigation

Netty 4.1.101.Final released

We are happy to announce the release of netty 4.1.101.Final. This is (mostly) a bug-fix release, which beside fixing correctness bugs also fixes a performance issue when DatagramChannel is used. If you use DatagramChannel you should consider the upgrade as soon as possible.

The most important changes are:

  • Add service-loaded extension points for channel initialization (#13565)
  • Added check for pseudo-headers in trailers (#13603)
  • Automatically close Http2StreamChannel when Http2FrameStreamExceptionreaches end ofChannelPipeline (#13651)
  • Throwing a stackless exception if RST_FRAME rate is exceeded (#13657)
  • Only enable the RST limit for servers by default (#13671)
  • Change default value of MAX_MESSAGES_PER_READ for DatagramChannel implementations (#13676)
  • Descriptive message for errors related to unknown http2 streams (#13691)

For more details please visit our bug tracker

Add service-loaded extension points for channel initialization

Netty is used by many libraries and frameworks that (reasonably) hide the fact that they use Netty under the covers. When Netty is hidden, it is hard, or sometimes impossible, to modify the channel pipelines, attributes, or options, from the outside. It might not even be clear if a framework or library makes use of Netty at all. However, we sometimes want to apply some changes, or make some checks, to most or all channels that are initialized by Netty, regardless of the framework or library that is using Netty in the given case.

Some examples of use-cases are:

  • Web application firewalls.
  • Server-side request forgery filters.
  • Intrusion detection.
  • Metrics gathering.

To address these use-cases in a way that don't require integrators to somehow find every Netty usage in a process, we introduce a service-loaded extension point that hooks into the channel initialization process. For more details on how this works and how this should be used see (#13565).

Thank You

Every idea and bug-report counts, and so we thought it is worth mentioning those who helped in this area.

Please report an unintended omission.