From 5741721f71f185872aa3d4860644d31df22ace1b Mon Sep 17 00:00:00 2001
From: Trustin Lee <trustin@gmail.com>
Date: Fri, 16 Apr 2010 13:32:55 +0000
Subject: [PATCH] Fixed a bug where HEAD response is not read completely if
 it's transfer encoding is 'chunked'.

---
 .../org/jboss/netty/handler/codec/http/HttpClientCodec.java | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/src/main/java/org/jboss/netty/handler/codec/http/HttpClientCodec.java b/src/main/java/org/jboss/netty/handler/codec/http/HttpClientCodec.java
index b960cf27c0..bf6a70e9b1 100644
--- a/src/main/java/org/jboss/netty/handler/codec/http/HttpClientCodec.java
+++ b/src/main/java/org/jboss/netty/handler/codec/http/HttpClientCodec.java
@@ -128,7 +128,11 @@ public class HttpClientCodec implements ChannelUpstreamHandler,
                 // message-body, even though the presence of entity-header fields
                 // might lead one to believe they do.
                 if (HttpMethod.HEAD.equals(method)) {
-                    return true;
+                    // Interesting edge case:
+                    // Zero-byte chunk will appear if Transfer-Encoding of the
+                    // response is 'chunked'.  This is probably because of the
+                    // trailing headers.
+                    return !msg.isChunked();
                 }
                 break;
             case 'C':