Am 18.11.2014 um 15:17 schrieb Christoph Läubrich:
You mostly see this because someone in the chain catches I/O Exceptions and wrapping them in some kind of other exception type (e.g. servlet exception), normally this type of exception is catched and ignored by jetty. This migth happen if connection get interrupted or user navigates away or closes browser...
Yes, I remember reading about this earlier, yet it's always a bit difficult to tell whether there are "real" issues (in example because of an external server or a proxy messing things up) or just an end user misbehaving all along the way. How do you deal with such exceptions - quietly discard these? Generally, for our operations this is sort of a problem, so I am tempted to not handle EofExceptions on upload at all - unless there's a meaningful way of figuring out what happened... :)
Anyway, thank you very much for yor feedback, greatly appreciated! Cheers, Kristian _______________________________________________ jetty-users mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/jetty-users
