[ChunkParser] does not handle additional headers fields after the message body.

[briantting]

It gets caught in a loop when processing chunked requests where there are additional headers fields after the message body. Occurs because:

1. The self.size in ChunkParser.process is 0
2. Thus the self.state is set to COMPLETE, but the len(data) > 0

[abhinavsingh]

Thanks, @briantting for reporting this and #45 . I am wondering what exactly is your use case that runs into these issues. Can you expand a little on that?

[briantting]

Hi Abhinav, I'm trying to run a series of web-platform-tests through a http proxy to test my code. The tests involve a lot of more unusual use cases that I've run into. Cheers, Brian

…

On Sun, Feb 24, 2019 at 9:53 AM Abhinav Singh ***@***.***> wrote: Thanks, @briantting <https://github.com/briantting> for reporting this and #45 <#45> . I am wondering what exactly is your use case that runs into these issues. Can you expand a little on that? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#44 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AB7Bg2t2_mo5tA3PfWFPkwGcO-Q-n-A-ks5vQtG2gaJpZM4bM5Ef> .

[abhinavsingh]

Thanks, @briantting, good to hear that. I observed issues you reported are encountered when packets are sent to proxy.py in a specific way, most likely if proxy.py is used in an automation environment.

[abhinavsingh]

@briantting Is it possible for you to give it another shot and/or provide raw requests being sent to proxy.py. Thank you.