-
Improvement
-
Resolution: Won't Do
-
Neutral
-
None
-
None
-
None
As described in MAGNOLIA-5112, we have a few places where we treat {{IOException}}s and basically just ignore them because they might be a sign for a client abort or broken pipe; we can't really do anything else because we don't want to be container-specific.
A possible improvement, however, would be to centralize this behavior - a possible solution to that is described and discussed in MAGNOLIA-3595.
This would allow for something a little smarter/safer; we don't want to replicate this code everywhere: other IOException should not be ignored.
- is related to
-
MGNLCACHE-48 Cache filter should rethrow exceptions instead of wrapping them (at least when unrelated)
- Closed
-
MAGNOLIA-3595 Add an exception handler for filters.
- Closed
-
MAGNOLIA-3566 Cache filter should ignore ClientAbortException
- Closed
-
MAGNOLIA-5112 Responses served from cache can throw a RuntimeException that should be ignored (Occasional broken pipe for DINWebPro.woff)
- Closed
-
MGNLIMG-162 Ignore ClientAbortExceptions (broken pipe) in ImagingServlet
- Closed