Go to file
Roelof Naude 757671b7cc Support empty http responses when using compression
Motivation:

Found a bug in that netty would generate a 20 byte body when returing a response
to an HTTP HEAD. the 20 bytes seems to be related to the compression footer.

RFC2616, section 9.4 states that responses to an HTTP HEAD MUST not return a message
body in the response.

Netty's own client implementation expected an empty response. The extra bytes lead to a
2nd response with an error decoder result:
java.lang.IllegalArgumentException: invalid version format: 14

Modifications:

Track the HTTP request method. When processing the response we determine if the response
is passthru unnchanged. This decision now takes into account the request method and passthru
responses related to HTTP HEAD requests.

Result:

Netty's http client works and better RFC conformance.
2015-05-26 09:55:34 +02:00
all [maven-release-plugin] prepare for next development iteration 2015-05-07 14:21:08 -04:00
buffer Expose metrics for PooledByteBufAllocator 2015-05-20 21:06:17 +02:00
codec [maven-release-plugin] prepare for next development iteration 2015-05-07 14:21:08 -04:00
codec-dns [maven-release-plugin] prepare for next development iteration 2015-05-07 14:21:08 -04:00
codec-haproxy [maven-release-plugin] prepare for next development iteration 2015-05-07 14:21:08 -04:00
codec-http Support empty http responses when using compression 2015-05-26 09:55:34 +02:00
codec-http2 Allow manual configuration of initial HTTP/2 SETTINGS frame. 2015-05-21 13:18:52 -07:00
codec-memcache [maven-release-plugin] prepare for next development iteration 2015-05-07 14:21:08 -04:00
codec-mqtt [maven-release-plugin] prepare for next development iteration 2015-05-07 14:21:08 -04:00
codec-socks [maven-release-plugin] prepare for next development iteration 2015-05-07 14:21:08 -04:00
codec-stomp [maven-release-plugin] prepare for next development iteration 2015-05-07 14:21:08 -04:00
codec-xml [maven-release-plugin] prepare for next development iteration 2015-05-07 14:21:08 -04:00
common [#3805] Fix incorrect javadoc in PlatformDependent 2015-05-25 21:42:31 +02:00
example SCTP echo client/server multi-homing examples 2015-05-22 22:24:09 +02:00
handler Allow writing with void promise if IdleStateHandler is configured in pipeline. 2015-05-25 21:09:47 +02:00
handler-proxy [maven-release-plugin] prepare for next development iteration 2015-05-07 14:21:08 -04:00
license Integrate non-blocking XML parser as Netty codec (#2806) 2015-02-19 13:46:14 +01:00
microbench [maven-release-plugin] prepare for next development iteration 2015-05-07 14:21:08 -04:00
resolver [maven-release-plugin] prepare for next development iteration 2015-05-07 14:21:08 -04:00
resolver-dns [maven-release-plugin] prepare for next development iteration 2015-05-07 14:21:08 -04:00
tarball [maven-release-plugin] prepare for next development iteration 2015-05-07 14:21:08 -04:00
testsuite [maven-release-plugin] prepare for next development iteration 2015-05-07 14:21:08 -04:00
testsuite-osgi [maven-release-plugin] prepare for next development iteration 2015-05-07 14:21:08 -04:00
transport Not try to write more then Integer.MAX_VALUE / SSIZE_MAX via writev 2015-05-21 12:02:10 +02:00
transport-native-epoll Not try to write more then Integer.MAX_VALUE / SSIZE_MAX via writev 2015-05-21 12:02:10 +02:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2015-05-07 14:21:08 -04:00
transport-sctp [maven-release-plugin] prepare for next development iteration 2015-05-07 14:21:08 -04:00
transport-udt [maven-release-plugin] prepare for next development iteration 2015-05-07 14:21:08 -04:00
.fbprefs
.gitignore
.travis.yml
CONTRIBUTING.md
LICENSE.txt
NOTICE.txt Integrate non-blocking XML parser as Netty codec (#2806) 2015-02-19 13:46:14 +01:00
pom.xml Upgrading Jetty alpn-api version 2015-05-22 13:13:14 -07:00
README.md
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.