I don't know if I'm the only one, but the cache module catches and logs this exception:

java.lang.RuntimeException: ClientAbortException: java.net.SocketException: Connection reset
at info.magnolia.module.cache.filter.CacheFilter.doFilter(CacheFilter.java:159)

It's a quite common exception, that in most cases means the browser has closed the connection. Ok, there are a few cases in which this may be useful to trace borderline problems with https and internet explorer, but I'd really like to have something to turn this off completely instead of having something harmless cluttering log file at error level...
Disabling the log completely for the cacheFilter class is not a good idea, and using the log4j extras to filter out a single exception isn't a good solution either.
The exception re-thrown from this filter is wrapped in a runtime exception, so it's not even immediate to catch and ignore those exceptions in another filter in the chain.