Go to file
Nolan O'Brien 6655a23440 Netty force encodes already encoded responses
Motivation:

Fix the regression recently introduced that causes already encoded responses to be encoded again as gzip

Modification:

instead of just looking for IDENTITY, anything set for Content-Encoding should be respected and left as-is

added unit tests to capture this use case

Result:

Fixes #6784
2017-05-27 08:30:14 +02:00
.github Use GitHub Issue/PR Template Feature 2016-12-07 11:40:46 -08:00
all [maven-release-plugin] prepare for next development iteration 2017-05-11 12:26:35 +02:00
bom Correctly include native modules 2017-05-18 07:07:34 +02:00
buffer [maven-release-plugin] prepare for next development iteration 2017-05-11 12:26:35 +02:00
codec [maven-release-plugin] prepare for next development iteration 2017-05-11 12:26:35 +02:00
codec-haproxy [maven-release-plugin] prepare for next development iteration 2017-05-11 12:26:35 +02:00
codec-http Netty force encodes already encoded responses 2017-05-27 08:30:14 +02:00
codec-socks [maven-release-plugin] prepare for next development iteration 2017-05-11 12:26:35 +02:00
common Share code that is needed to support shaded native libraries. 2017-05-19 19:34:03 +02:00
dev-tools [maven-release-plugin] prepare for next development iteration 2017-05-11 12:26:35 +02:00
example [maven-release-plugin] prepare for next development iteration 2017-05-11 12:26:35 +02:00
handler SslHandler#handlerRemoved0() shouldn't care about the SSLEngine being a specific type but only if it's ReferenceCounted 2017-05-19 19:32:18 +02:00
license Remove reference to akka code and ArrayDeque which is not part of netty anymore 2017-03-07 21:32:36 +01:00
microbench Optimizations in NetUtil 2017-05-18 16:51:44 -07:00
tarball [maven-release-plugin] prepare for next development iteration 2017-05-11 12:26:35 +02:00
testsuite Fix handle of ByteBuf with multi nioBuffer in EpollDatagramChannel 2017-05-26 13:37:25 +02:00
testsuite-autobahn [maven-release-plugin] prepare for next development iteration 2017-05-11 12:26:35 +02:00
testsuite-osgi [maven-release-plugin] prepare for next development iteration 2017-05-11 12:26:35 +02:00
transport [maven-release-plugin] prepare for next development iteration 2017-05-11 12:26:35 +02:00
transport-native-epoll Fix handle of ByteBuf with multi nioBuffer in EpollDatagramChannel 2017-05-26 13:37:25 +02:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2017-05-11 12:26:35 +02:00
transport-sctp Fix parameter order in SctpOutboundByteStreamHandler. 2017-05-25 09:29:58 +02:00
transport-udt [maven-release-plugin] prepare for next development iteration 2017-05-11 12:26:35 +02:00
.fbprefs Updated Find Bugs configuration 2009-03-04 10:33:09 +00:00
.gitignore Use shaded dependency on JCTools instead of copy and paste 2016-06-10 13:53:28 +02: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 reference to akka code and ArrayDeque which is not part of netty anymore 2017-03-07 21:32:36 +01:00
pom.xml [maven-release-plugin] prepare for next development iteration 2017-05-11 12:26:35 +02:00
README.md Updating Branches to look section to match the current branching structure of the project 2016-03-10 22:09:30 +01:00
run-example.sh Add UptimeServer and adjust UptimeClient's code style. 2017-04-28 07:50:53 +02: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

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.