HTTP server message followed by junk closes before reply

[Wade Poziombka]

Wade Poziombka wrote:
> 
> The issue is that the HTTP codec notes decoding error before the reply for
> the first valid message is sent.
> 

I guess I was not clear... the problem is that the channel is closed before
the reply goes back.  It seems we should be able to defer the close.  The
fact that the codec detected the error is not an issue.  The fact that it
closes seems to be.

-- 
View this message in context: http://n2.nabble.com/HTTP-server-message-followed-by-junk-closes-before-reply-tp2315995p2316268.html
Sent from the Netty User Group mailing list archive at Nabble.com.