https://bz.apache.org/bugzilla/show_bug.cgi?id=68634
--- Comment #2 from Remy Maucherat <r...@apache.org> --- Ok, the ApplicationDispatcher forward does something different for a ResponseFacade, so it can mess up your timing. Obviously if the response is simply a ResponseFacade it gets suspended (pretending to be done) and things continue nicely, otherwise it gets immediately closed (there is no other way to enforce the specification requirements that a response is done following a forward; at this point the client gets the full response and can move on). Maybe an effort could be made to unwrap and find the ResponseFacade, and only if not found close. This is really old code. It is not a good idea to rely too much on this however, since anything in your app that will close the response would do the exact same behavior. Please use session pinning instead, to comply with the servlet specification. -- 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
