Go to file
Scott Mitchell 35b0cd58fb HTTP/2 write of released buffer should not write and should fail the promise
Motivation:
HTTP/2 allows writes of 0 length data frames. However in some cases EMPTY_BUFFER is used instead of the actual buffer that was written. This may mask writes of released buffers or otherwise invalid buffer objects. It is also possible that if the buffer is invalid AbstractCoalescingBufferQueue will not release the aggregated buffer nor fail the associated promise.

Modifications:
- DefaultHttp2FrameCodec should take care to fail the promise, even if releasing the data throws
- AbstractCoalescingBufferQueue should release any aggregated data and fail the associated promise if something goes wrong during aggregation

Result:
More correct handling of invalid buffers in HTTP/2 code.
2017-11-06 14:38:58 -08:00
.github Use GitHub Issue/PR Template Feature 2016-12-07 11:40:26 -08:00
all Update links for actual Protobuf repo and documentation 2017-10-23 07:41:35 +02:00
bom [maven-release-plugin] prepare for next development iteration 2017-09-25 06:12:32 +02:00
buffer Make methods 'static' where it possible 2017-10-21 14:59:26 +02:00
codec HttpObjectEncoder and MessageAggregator EMPTY_BUFFER usage 2017-11-03 07:03:19 +01:00
codec-dns [maven-release-plugin] prepare for next development iteration 2017-09-25 06:12:32 +02:00
codec-haproxy Do not treat errors as decoder exception (redux) 2017-10-07 18:17:00 +02:00
codec-http Correctly handle WebSockets 00 when using HttpClientCodec. 2017-11-03 15:55:22 +01:00
codec-http2 HTTP/2 write of released buffer should not write and should fail the promise 2017-11-06 14:38:58 -08:00
codec-memcache [maven-release-plugin] prepare for next development iteration 2017-09-25 06:12:32 +02:00
codec-mqtt [maven-release-plugin] prepare for next development iteration 2017-09-25 06:12:32 +02:00
codec-redis [maven-release-plugin] prepare for next development iteration 2017-09-25 06:12:32 +02:00
codec-smtp [maven-release-plugin] prepare for next development iteration 2017-09-25 06:12:32 +02:00
codec-socks Do not treat errors as decoder exception (redux) 2017-10-07 18:17:00 +02:00
codec-stomp [maven-release-plugin] prepare for next development iteration 2017-09-25 06:12:32 +02:00
codec-xml [maven-release-plugin] prepare for next development iteration 2017-09-25 06:12:32 +02:00
common Support running Netty in bootstrap class loader 2017-10-29 13:13:19 +01:00
dev-tools [maven-release-plugin] prepare for next development iteration 2017-09-25 06:12:32 +02:00
example Make methods 'static' where it possible 2017-10-21 14:59:26 +02:00
handler HTTP/2 write of released buffer should not write and should fail the promise 2017-11-06 14:38:58 -08:00
handler-proxy [maven-release-plugin] prepare for next development iteration 2017-09-25 06:12:32 +02:00
license Remove reference to akka code and ArrayDeque which is not part of netty anymore 2017-03-07 21:30:51 +01:00
microbench Optimistically update ref counts 2017-10-04 08:42:33 +02:00
resolver [maven-release-plugin] prepare for next development iteration 2017-09-25 06:12:32 +02:00
resolver-dns DnsResolver CNAME redirect bug 2017-10-23 09:37:32 -07:00
tarball [maven-release-plugin] prepare for next development iteration 2017-09-25 06:12:32 +02:00
testsuite [maven-release-plugin] prepare for next development iteration 2017-09-25 06:12:32 +02:00
testsuite-autobahn [maven-release-plugin] prepare for next development iteration 2017-09-25 06:12:32 +02:00
testsuite-osgi [maven-release-plugin] prepare for next development iteration 2017-09-25 06:12:32 +02:00
transport HTTP/2 write of released buffer should not write and should fail the promise 2017-11-06 14:38:58 -08:00
transport-native-epoll Revert "Set readPending to false when ever a read is done" 2017-11-06 09:21:42 -08:00
transport-native-kqueue Revert "Set readPending to false when ever a read is done" 2017-11-06 09:21:42 -08:00
transport-native-unix-common Ensure setting / getting the traffic class on an ipv4 only system works when using the native transport. 2017-10-24 09:03:28 +02:00
transport-native-unix-common-tests Ensure setting / getting the traffic class on an ipv4 only system works when using the native transport. 2017-10-24 09:03:28 +02:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2017-09-25 06:12:32 +02:00
transport-sctp [maven-release-plugin] prepare for next development iteration 2017-09-25 06:12:32 +02:00
transport-udt [maven-release-plugin] prepare for next development iteration 2017-09-25 06:12:32 +02:00
.fbprefs Updated Find Bugs configuration 2009-03-04 10:33:09 +00:00
.gitignore Use shaded dependency on JCTools instead of copy and paste 2016-06-10 13:19:45 +02:00
.travis.yml Travis CI branch whitelisting 2013-03-11 09:55:43 +09:00
CONTRIBUTING.md Move the pull request guide to the developer guide 2014-03-12 13:13:58 +09:00
LICENSE.txt Relicensed to Apache License v2 2009-08-28 07:15:49 +00:00
NOTICE.txt Remove reference to akka code and ArrayDeque which is not part of netty anymore 2017-03-07 21:30:51 +01:00
pom.xml OpenSslEngine support unwrap plaintext greater than 2^14 and avoid 2017-11-02 11:42:38 -07:00
README.md Updating Branches to look section to match the current branching structure of the project 2016-03-10 22:08:01 +01:00
run-example.sh Add UptimeServer and adjust UptimeClient's code style. 2017-04-28 07:41:07 +02:00

Netty Project

Netty is an asynchronous event-driven network application framework for rapid development of maintainable high performance protocol servers & clients.

How to build

For the detailed information about building and developing Netty, please visit the developer guide. This page only gives very basic information.

You require the following to build Netty:

Note that this is build-time requirement. JDK 5 (for 3.x) or 6 (for 4.0+) is enough to run your Netty-based application.

Branches to look

Development of all versions takes place in each branch whose name is identical to <majorVersion>.<minorVersion>. For example, the development of 3.9 and 4.0 resides in the branch '3.9' and the branch '4.0' respectively.