Wrap disconnected client exceptions as AsyncRequestNotUsableException in Servlet container onError callback #34363
Labels
in: web
Issues in web modules (web, webmvc, webflux, websocket)
type: enhancement
A general enhancement
Milestone
We raise this in
StandardServletAsyncWebRequest
when wrapped response I/O methods catch anIOException
. However, the Servlet container may be first in reporting the same viaAsyncListener#onError
in which case@ExceptionHandler
methods see the rawIOException
making it more difficult to differentiate from any other I/O error.We should also apply the
AsyncRequestNotUsableException
wrapper inWebAsyncManager
, inonError
handling for exceptions recognized withDisconnectedClientHelper
.Originally reported in #34005.
The text was updated successfully, but these errors were encountered: