From d220afa8858d8945db681000dd3332a4dca7f838 Mon Sep 17 00:00:00 2001 From: Roelof Naude Date: Mon, 10 Nov 2014 12:57:02 +0200 Subject: [PATCH] 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. --- .../netty/handler/codec/http/HttpContentEncoder.java | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/codec-http/src/main/java/io/netty/handler/codec/http/HttpContentEncoder.java b/codec-http/src/main/java/io/netty/handler/codec/http/HttpContentEncoder.java index 210e0339f4..2e9b7f034e 100644 --- a/codec-http/src/main/java/io/netty/handler/codec/http/HttpContentEncoder.java +++ b/codec-http/src/main/java/io/netty/handler/codec/http/HttpContentEncoder.java @@ -87,7 +87,12 @@ public abstract class HttpContentEncoder extends MessageToMessageCodec