Netty has problem to deal with the "Connection: close" message ... We cannot read the content.

[Huican Ping]

More information:

The messageReceived() message is same logic as the ones at http example
where it does 
check "respStatus.getCode() == 200 && resp.isChunked() "

I noticed for the headers at 100th response:
	HTTP/1.1 200 OK
	Server: Apache-Coyote/1.1
	Content-Type: text/xml;charset=UTF-8
	Date: Tue, 02 Jun 2009 15:50:12 GMT
	Connection: close

That resp.isChunked() returns true !! While stepping into the code (at
DefaultHttpMessage.java isChunked() method), and I dumpped out headers, it
has Transfer-Encoding (which I don't know who added it mysteriously).
  {Connection=[close], Content-Type=[text/xml;charset=UTF-8], Date=[Tue, 02
Jun 2009 18:29:59 GMT], Server=[Apache-Coyote/1.1],
Transfer-Encoding=[chunked]}



Huican Ping wrote:
> 
> I am using the 3.1.0.Beta3.
> 
> That 100th message has no "content-length" header, but has "connection:
> close" inside. It is still a valid message.
> 
> Any suggestion or workaround?
> 

-- 
View this message in context: http://n2.nabble.com/Netty-has-problem-to-deal-with-the-%22Connection%3A-close%22-message-...-We-cannot-read-the-content.-tp3013392p3013922.html
Sent from the Netty User Group mailing list archive at Nabble.com.