Netty Project

We are happy to announce the release of the third alpha for the upcoming netty version 4.2.0. Everyone using netty 4.1.x should be able to upgrade to 4.2.0.Alpha2 without any API breakage. The only new requirement is JDK8 or later. We encourage ... [More] users of netty 4.1.x to try out this alpha release and so provide feedback if any breakage is noticed. This will help us to be aware of any problems early in the release cycle. That said, be aware that this is only an alpha release and so shouldn't be considered for production usage. Netty 4.2.0 will come with some... [Less]

We are happy to announce the release of netty-incubator-codec-ohttp 0.0.14.Final. This release is a bug-fix release. The most important changes are: Validate that header names are only lowercase (#81) Add utility class which contains methods ... [More] which helps to convert HTTP/1.x to BHTTP messages (#82) For more details related to this release see our bug-tracker.... [Less]

We are happy to announce the release of netty-incubator-codec-quic 0.0.66.Final. The most important changes are: QuicTokenHandler: expose max connection id length, fix endianness (#732) Correctly translate quiche error to QuicException that have ... [More] no transport error mappings (#736) Upgrade to netty 4.1.112.Final (#737) For more details related to this release see our bug-tracker. For more details about this codec in general please read our initial announcement. 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. @makkarpov @normanmaurer... [Less]

We are happy to announce the release of netty 4.1.112.Final. This is a bug-fix release. The most important changes are: Avoid unnecessary reflective probes on netty initialization (#14107) Allow control frames between fragments (#14122) Only ... [More] delete the socket file for NioServerDomainSocketChannel (#14134) Add check for IPv6 brackets when address is unresolved (#14141) fix ResolvConf initialization with SecurityManager enabled (#14154) Fix potential DNS cache invalidation in ResolveWithDotSearchDomain scenario (#14171) Backport the SslContextBuilder.endpointIdentificationAlgorithm method (#14174) Aggressively remove PoolThreadCache references from its finalizer object (#14155) Send Http2PriorityFrame through fireUserEventTriggered for Http2MultiplexHandler (#14168) Fix potential DNS cache invalidation across different EventLoops (#14147) Reject http header values with non SP / HTAB chars (#14178) Don't strip whitespaces from... [Less]

We are happy to announce the release of netty-incubator-codec-ohttp 0.0.13.Final. This release contains a fix for CVE-2024-40642, so we encourage everyone to upgrade as fast as possible. The most important changes are: CVE-2024-40642 Ensure ... [More] BoringSSLAsymmetricCipherKeyPair will eventually release native memory (#77) For more details related to this release see our bug-tracker.... [Less]

We are happy to announce the release of netty-incubator-codec-ohttp 0.0.12.Final. This release is a bug-fix release. The most important changes are: Correctly release native resources in JNI code (#65) Don't leak native memory for random ... [More] generated keys (#66) Correctly detect when allocation fails and return correct (#67) Add cache digest on creation of BoringSSLHPKEContext (#68) Use constant-time equals for private key material (#69) Add missing equals / hashCode implementations (#70) Correctly implement encoding / decoding Key Configuration Media Type (#75) For more details related to this release see our bug-tracker.... [Less]

We are happy to announce the release of the second alpha for the upcoming netty version 4.2.0. Everyone using netty 4.1.x should be able to upgrade to 4.2.0.Alpha2 without any API breakage. The only new requirement is JDK8 or later. We encourage ... [More] users of netty 4.1.x to try out this alpha release and so provide feedback if any breakage is noticed. This will help us to be aware of any problems early in the release cycle. That said, be aware that this is only an alpha release and so shouldn't be considered for production usage. Netty 4.2.0 will come with some... [Less]

We are happy to announce the release of netty-incubator-codec-quic 0.0.65.Final. The most important changes are: Don't use Quiche to parse QUIC packet (#724) Upgrade to netty-4.1.111.Final (#725) initial congestion window configuration (#726) ... [More] Update to quiche 0.22.0 (#730) For more details related to this release see our bug-tracker. For more details about this codec in general please read our initial announcement. 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. @normanmaurer @poisonriver... [Less]

We are happy to announce the release of the first alpha for the upcoming netty version 4.2.0. Everyone using netty 4.1.x should be able to upgrade to 4.2.0.Alpha1 without any API breakage. The only new requirement is JDK8 or later. This release has ... [More] all the fixes that are also included in 4.1.111.Final. We encourage users of netty 4.1.x to try out this alpha release and so provide feedback if any breakage is noticed. This will help us to be aware of any problems early in the release cycle. That said, be aware that this is only an alpha release and... [Less]

We are happy to announce the release of netty 4.1.111.Final. This is a bug-fix release. The most important changes are: ReadOnlyByteBufferBuf | ReadOnlyUnsafeDirectByteBuf get, copy, duplicate, slice methods should be safe to be called from ... [More] multiple threads (#14072) ReadyOnlyBuf must return false for isWritable() when sliced or duplicated (#14071) ReadOnlyByteBuf (and sub-classes) does not create derived buffers that share reference count (#14076) ByteBuf.asReadOnly().nioBuffer*() need to return read-only ByteBuffer (#14078) Remove unwanted mandatory dependency in OSGi (#14082) HashedWheelTimer.stop() must cancel tasks (#14083) ZSTD decompression not resilient to compression bombs (#14004) Duplicate of slice should have the same capacity as the original slice so that it's not writable (#14093) Optimize wrap buffer... [Less]