https://issues.apache.org/bugzilla/show_bug.cgi?id=56190
--- Comment #8 from Mark Thomas <ma...@apache.org> --- I've been back and re-read both the Servlet 3.0 and Servlet 3.1 specifications. I don't know where I got the idea from that the response always had to be writable after the call to complete() but that is clearly wrong. There is the requirement that when called before the container-initiated dispatch that called startAsync() has returned to the container then the complete() call doesn't take effect until after that thread returns but when it does take effect it still needs to close the response. I'll take a look at getting this fixed. This might break some applications (it might even break some of our test cases) but the spec is clear on the required behavior so I think any such breakage is acceptable. -- 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
