https://bz.apache.org/bugzilla/show_bug.cgi?id=64974
--- Comment #5 from Remy Maucherat <r...@apache.org> --- (In reply to Mark Thomas from comment #4) > I have a test case that replicates this now and some ideas for a potential > fix. > > Combining async and pipelining does seem an odd thing to do but I don't see > any spec language that would prevent it. It still doesn't make sense to me and I still don't see how it really happens with input that means something and an application that doesn't actively tries to mess up its input. I think the code in Http11InputBuffer.available(boolean read) could likely use InputFilter.isFinished to avoid the edge case. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
