https://bz.apache.org/bugzilla/show_bug.cgi?id=69121
Mark Thomas <ma...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |NEEDINFO
--- Comment #1 from Mark Thomas <ma...@apache.org> ---
I'm leaning towards closing this as WONTFIX but I am leaving it open in case
there is an aspect of this report that I have missed.
I would expect Tomcat to forward to the default error page if the connection to
the client is lost whether async is being used or not.
The referenced commit was to ensure that that did not happen when an async
application was handling an error and dispatched to to specific target.
I suspect that you are seeing a dispatch from onError that is now being
performed correctly and that the target of that dispatch is failing which in
turn is triggering the default error page. If all of that is true, then that is
working as intended. If not, please provide the simplest possible test case -
ideally in the same form as the Tomcat unit tests - that demonstrates the issue
and include an explanation of why you think it isn't specification compliant.
--
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
