[ http://issues.apache.org/jira/browse/WICKET-155?page=all ]
Eelco Hillenius updated WICKET-155:
-----------------------------------
Component/s: wicket
> Extend cases where the exception can be ignored due to an aborted request
> -------------------------------------------------------------------------
>
> Key: WICKET-155
> URL: http://issues.apache.org/jira/browse/WICKET-155
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Affects Versions: 1.2.4, 1.3, 2.0
> Reporter: Eelco Hillenius
> Assigned To: Johan Compagner
>
> We should either find more specific catches in Resource#respond or come up
> with some other way to ensure we can recognize a client abortion. For
> instance, Jetty 6 on unix-like platforms (tested here on OpenBSD/ OSX) throws
> EofExceptions which extend IOExceptions and thus are not marked as ignorable.
> The problem then is that a stack trace will be printed in
> ComponentResourceRequestTarget, and as many production systems will have some
> trigger installed that sends an error message/ SMS/ ... that can be quite
> annoying.
> Can't we instead of looking at the exception somehow look at the request/
> response itself to figure out that a request was aborted? If that is
> possible, that seems like a much more robust way of solving this.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
