EOFExceptions from server code are incorrectly assumed to indicate a client disconnection and are swallowed

[sddavis]

I have an application that allows users to upload a JSON file and parses it using Gson. If the file is invalid, Gson may throw a java.io.EOFException. Starting with spring-framework 6.2, due to 9252e74, Spring assumes this means the client disconnected and swallows the exception, returning a 200 response and breaking client-side error handling.

To work around this, I would need to handle EOFException in every place that can throw it, replacing it with a different exception.