Go to file
nmittler 8cd259896e No HTTP/2 RST_STREAM if no prior HEADERS were sent
Motivation:

Because we flow control HEADERS frames, it's possible that an intermediate error can result in a RST_STREAM frame being sent for a frame that the other endpoint is not yet aware of. This is a violation of the spec and will either result in spammy logs at the other endpoint or broken connections.

Modifications:

Modified the HTTP/2 handler so that it only sends RST_STREAM if it has sent at least one HEADERS frame to the remote endpoint for the stream.

Result:

Fixes #4465
2015-11-25 13:46:32 -08:00
all [maven-release-plugin] prepare for next development iteration 2015-11-10 22:59:33 +01:00
buffer Fix setBytes on read-only ByteBuffer 2015-11-17 22:45:37 -08:00
codec Adjustable size of DefaultHeaders array 2015-11-23 15:38:08 -08:00
codec-dns [maven-release-plugin] prepare for next development iteration 2015-11-10 22:59:33 +01:00
codec-haproxy [maven-release-plugin] prepare for next development iteration 2015-11-10 22:59:33 +01:00
codec-http [#4331] Helper methods to get charset from Content-Type header of HttpMessage 2015-11-19 15:59:34 -08:00
codec-http2 No HTTP/2 RST_STREAM if no prior HEADERS were sent 2015-11-25 13:46:32 -08:00
codec-memcache [maven-release-plugin] prepare for next development iteration 2015-11-10 22:59:33 +01:00
codec-mqtt [maven-release-plugin] prepare for next development iteration 2015-11-10 22:59:33 +01:00
codec-socks [maven-release-plugin] prepare for next development iteration 2015-11-10 22:59:33 +01:00
codec-stomp [maven-release-plugin] prepare for next development iteration 2015-11-10 22:59:33 +01:00
codec-xml [maven-release-plugin] prepare for next development iteration 2015-11-10 22:59:33 +01:00
common DefaultPromise LateListener notification order 2015-11-20 09:30:35 -08:00
example [maven-release-plugin] prepare for next development iteration 2015-11-10 22:59:33 +01:00
handler Use OneTimeTask where possible to reduce object creation 2015-11-20 14:39:06 -08:00
handler-proxy [maven-release-plugin] prepare for next development iteration 2015-11-10 22:59:33 +01:00
license [#4331] Helper methods to get charset from Content-Type header of HttpMessage 2015-11-19 15:59:34 -08:00
microbench Backport of benchmark broke build 2015-11-20 15:03:50 -08:00
resolver [maven-release-plugin] prepare for next development iteration 2015-11-10 22:59:33 +01:00
resolver-dns [maven-release-plugin] prepare for next development iteration 2015-11-10 22:59:33 +01:00
tarball [maven-release-plugin] prepare for next development iteration 2015-11-10 22:59:33 +01:00
testsuite [maven-release-plugin] prepare for next development iteration 2015-11-10 22:59:33 +01:00
testsuite-osgi [maven-release-plugin] prepare for next development iteration 2015-11-10 22:59:33 +01:00
transport Fixing spammy logging for CoalescingBufferQueueTest 2015-11-25 07:16:05 -08:00
transport-native-epoll Lazy Initialization of epoll splice queue 2015-11-20 15:09:53 -08:00
transport-rxtx Use OneTimeTask where possible to reduce object creation 2015-11-20 14:39:06 -08:00
transport-sctp Use OneTimeTask where possible to reduce object creation 2015-11-20 14:39:06 -08:00
transport-udt [maven-release-plugin] prepare for next development iteration 2015-11-10 22:59:33 +01:00
.fbprefs Updated Find Bugs configuration 2009-03-04 10:33:09 +00:00
.gitignore Add JVM crash logs to .gitignore 2014-05-18 21:36:54 +09: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 [#4331] Helper methods to get charset from Content-Type header of HttpMessage 2015-11-19 15:59:34 -08:00
pom.xml update pom due to alpn provided 2015-11-23 12:52:51 -08:00
README.md Fix the 'branches to look' section 2015-10-27 13:59:11 +01:00
run-example.sh Add HTTP/2 Netty tiles example 2015-05-18 14:16:54 -07: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

The 'master' branch is where the development of the latest major version lives on. The development of all other 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.