Trustin Lee 24fc1b9b37 Fix a bug where HttpObjectDecoder generates two LastHttpContent consecutively ... Motivation: When an HttpResponseDecoder decodes an invalid chunk, a LastHttpContent instance is produced and the decoder enters the 'BAD_MESSAGE' state, which is not supposed to produce a message any further. However, because HttpObjectDecoder.invalidChunk() did not clear this.message out to null, decodeLast() will produce another LastHttpContent message on a certain situation. Modification: Do not forget to null out HttpObjectDecoder.message in invalidChunk(), and add a test case for it. Result: No more consecutive LastHttpContent messages produced by HttpObjectDecoder.		2014-02-26 15:53:53 -08:00
..
src	Fix a bug where HttpObjectDecoder generates two LastHttpContent consecutively	2014-02-26 15:53:53 -08:00
pom.xml	Update the version to 4.1.0.Alpha1-SNAPSHOT	2014-02-13 18:32:26 -08:00