Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Netty project - an event-driven asynchronous network application framework
Java Other
branch: master

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.
latest commit 89f8dace60
@naude-r naude-r authored normanmaurer committed
Failed to load latest commit information.
all [maven-release-plugin] prepare for next development iteration
buffer Expose metrics for PooledByteBufAllocator
codec-dns Fix missing ResourceLeak.close() in AbstractDnsMessage
codec-haproxy ByteString introduced as AsciiString super class
codec-http Support empty http responses when using compression
codec-http2 Allow manual configuration of initial HTTP/2 SETTINGS frame.
codec-memcache Returns after encoding each message not do check following instance t…
codec-mqtt [maven-release-plugin] prepare for next development iteration
codec-socks [maven-release-plugin] prepare for next development iteration
codec-stomp ByteString introduced as AsciiString super class
codec-xml [maven-release-plugin] prepare for next development iteration
codec Remove memory copy when extract frame in LengthFieldBasedFrameDecoder
common [#3805] Fix incorrect javadoc in PlatformDependent
example SCTP echo client/server multi-homing examples
handler-proxy ByteString introduced as AsciiString super class
handler Allow writing with void promise if IdleStateHandler is configured in …
license Integrate non-blocking XML parser as Netty codec (#2806)
microbench Have Http2LocalFlowController.consumeBytes indicate whether a WINDOW_…
resolver-dns Revamp DNS codec
resolver Use InetSocketAddress.getHostName() instead of getHostString()
tarball [maven-release-plugin] prepare for next development iteration
testsuite-osgi Upgrade twitter hpack dependency
testsuite Fix compile error introduced by cherry-pick edf1eb1
transport-native-epoll Not try to write more then Integer.MAX_VALUE / SSIZE_MAX via writev
transport-rxtx [maven-release-plugin] prepare for next development iteration
transport-sctp Add support for SCTP 'unordered' flag.
transport-udt Remove duplicated code in AcceptorChannel classes.
transport Not try to write more then Integer.MAX_VALUE / SSIZE_MAX via writev
.fbprefs Updated Find Bugs configuration
.gitignore Exclude bin directory from git Motivation:
.travis.yml Travis CI branch whitelisting
CONTRIBUTING.md Move the pull request guide to the developer guide
LICENSE.txt Relicensed to Apache License v2
NOTICE.txt Integrate non-blocking XML parser as Netty codec (#2806)
README.md Add a link to the 'native transports' page
pom.xml Upgrading Jetty alpn-api version
run-example.sh Add HTTP/2 Netty tiles example

README.md

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:

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.

Something went wrong with that request. Please try again.