Go to file
Trustin Lee 0d210f45f2 Fix a bug where HttpObjectDecoder generates two LastHttpContent consecutively
Motivation:
When an HttpResponseDecoder decodes an invalid chunk, a LastHttpContent instance is produced and the decoder enters the 'BAD_MESSAGE' state, which is not supposed to produce a message any further.  However, because HttpObjectDecoder.invalidChunk() did not clear this.message out to null, decodeLast() will produce another LastHttpContent message on a certain situation.

Modification:
Do not forget to null out HttpObjectDecoder.message in invalidChunk(), and add a test case for it.

Result:
No more consecutive LastHttpContent messages produced by HttpObjectDecoder.
2014-02-26 15:54:33 -08:00
all [maven-release-plugin] prepare for next development iteration 2014-02-24 15:39:26 +01:00
buffer [maven-release-plugin] prepare for next development iteration 2014-02-24 15:39:26 +01:00
codec [maven-release-plugin] prepare for next development iteration 2014-02-24 15:39:26 +01:00
codec-http Fix a bug where HttpObjectDecoder generates two LastHttpContent consecutively 2014-02-26 15:54:33 -08:00
codec-socks [maven-release-plugin] prepare for next development iteration 2014-02-24 15:39:26 +01:00
common [maven-release-plugin] prepare for next development iteration 2014-02-24 15:39:26 +01:00
example [maven-release-plugin] prepare for next development iteration 2014-02-24 15:39:26 +01:00
handler [maven-release-plugin] prepare for next development iteration 2014-02-24 15:39:26 +01:00
license Add back jzlib license file and notice 2013-02-21 14:00:59 -08:00
microbench [maven-release-plugin] prepare for next development iteration 2014-02-24 15:39:26 +01:00
tarball [maven-release-plugin] prepare for next development iteration 2014-02-24 15:39:26 +01:00
testsuite [maven-release-plugin] prepare for next development iteration 2014-02-24 15:39:26 +01:00
transport [maven-release-plugin] prepare for next development iteration 2014-02-24 15:39:26 +01:00
transport-native-epoll [maven-release-plugin] prepare for next development iteration 2014-02-24 15:39:26 +01:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2014-02-24 15:39:26 +01:00
transport-sctp [maven-release-plugin] prepare for next development iteration 2014-02-24 15:39:26 +01:00
transport-udt [maven-release-plugin] prepare for next development iteration 2014-02-24 15:39:26 +01:00
.fbfilter.xml Update license headers 2012-06-04 13:31:44 -07:00
.fbprefs Updated Find Bugs configuration 2009-03-04 10:33:09 +00:00
.gitignore Format and partially describe Gitignore 2013-12-10 07:04:38 +01:00
.travis.yml Travis CI branch whitelisting 2013-03-11 09:55:43 +09:00
LICENSE.txt Relicensed to Apache License v2 2009-08-28 07:15:49 +00:00
NOTICE.txt Add back jzlib license file and notice 2013-02-21 14:00:59 -08:00
pom.xml [maven-release-plugin] prepare for next development iteration 2014-02-24 15:39:26 +01:00
README.md Update README.md 2014-01-16 14:38:36 +09: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 major versions takes place in each branch whose name is identical to its major version number. For example, the development of 3.x and 4.x resides in the branch '3' and the branch '4' respectively.