andreacavalli/netty5
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
6,036 Commits 27 Branches 234 Tags 84 MiB
Java 99.8%
Shell 0.1%
eca194daf4
Go to file
Roelof Naude eca194daf4 Cater for empty response bodies when performing response compression. 
Motivation:
RFC 2616, 4.3 Message Body states that:
All 1xx (informational), 204 (no content), and 304 (not modified) responses MUST NOT include a
message-body. All other responses do include a message-body, although it MAY be of zero length.

Modifications:
HttpContentEncoder was previously modified to cater for HTTP 100 responses. This check is enhanced to
include HTTP 204 and 304 responses.

Result:
Empty response bodies will not be modified to include the compression footer. This footer messed with Chrome's
response parsing leading to "hanging" requests.
2014-11-13 08:16:43 +01:00
all [maven-release-plugin] prepare for next development iteration 2014-10-29 11:48:40 +01:00
buffer [maven-release-plugin] prepare for next development iteration 2014-10-29 11:48:40 +01:00
codec HTTP Content Encoder allow EmptyLastHttpContent 2014-11-05 23:23:21 -05:00
codec-http Cater for empty response bodies when performing response compression. 2014-11-13 08:16:43 +01:00
codec-socks [maven-release-plugin] prepare for next development iteration 2014-10-29 11:48:40 +01:00
common Handle the interface name in IPv6 address correctly 2014-11-12 12:15:14 +09:00
example Backport ALPN and Mutual Auth SSL 2014-10-31 14:15:12 +09:00
handler Add ApplicationProtocolConfig.DISABLED 2014-10-31 14:15:43 +09:00
license Remove license of deque as we not use it anymore 2014-08-04 12:21:33 +02:00
microbench Benchmark for HttpRequestDecoder 2014-11-12 14:37:11 +01:00
tarball [maven-release-plugin] prepare for next development iteration 2014-10-29 11:48:40 +01:00
testsuite [maven-release-plugin] prepare for next development iteration 2014-10-29 11:48:40 +01:00
transport Add generic versions of PromiseAggregator and PromiseNotifier. 2014-11-07 08:44:20 +01:00
transport-native-epoll [maven-release-plugin] prepare for next development iteration 2014-10-29 11:48:40 +01:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2014-10-29 11:48:40 +01:00
transport-sctp [maven-release-plugin] prepare for next development iteration 2014-10-29 11:48:40 +01:00
transport-udt [maven-release-plugin] prepare for next development iteration 2014-10-29 11:48:40 +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:37:12 +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:18:14 +09:00
LICENSE.txt Relicensed to Apache License v2 2009-08-28 07:15:49 +00:00
NOTICE.txt Remove license of deque as we not use it anymore 2014-08-04 12:21:33 +02:00
pom.xml Fix build errors introduced during backporting SslContext 2014-10-31 14:25:14 +09:00
README.md Add a link to the 'native transports' page 2014-07-21 12:54:43 -07:00
run-example.sh Use a forked exec-maven-plugin instead of maven-antrun-plugin 2014-05-23 20:06:12 +09:00

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 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.