72a216625f
Motivation: According to RFC 7231 the server may choose to: ``` indicate a zero-length payload for the response by including a Transfer-Encoding header field with a value of chunked and a message body consisting of a single chunk of zero-length ``` https://tools.ietf.org/html/rfc7231#page-53 In such cases the exception below appears during decoding phase: ``` java.lang.IllegalArgumentException: invalid version format: 0 at io.netty.handler.codec.http.HttpVersion.<init>(HttpVersion.java:121) at io.netty.handler.codec.http.HttpVersion.valueOf(HttpVersion.java:76) at io.netty.handler.codec.http.HttpResponseDecoder.createMessage(HttpResponseDecoder.java:118) at io.netty.handler.codec.http.HttpObjectDecoder.decode(HttpObjectDecoder.java:219) ``` Modifications: HttpObjectDecoder.isContentAlwaysEmpty specifies content NOT empty when 205 Reset Content response Result: There is no `IllegalArgumentException: invalid version format: 0` when handling 205 Reset Content response with transfer-encoding
Netty Project
Netty is an asynchronous event-driven network application framework for rapid development of maintainable high performance protocol servers & clients.
Links
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:
- Latest stable Oracle JDK 7
- Latest stable Apache Maven
- If you are on Linux, you need additional development packages installed on your system, because you'll build the native transport.
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.