ClientAbortException if client (Browser) drops connection (WebFlux)
Mmkldb opened this issue · 2 comments
Description
We using Spring WebFlux to with ServerSentEvents to provide continuously data to the client browser.
When client browser drops the connection is this only detectable by the server through a failed transmission of new data.
This is beside the normal stateless communication between browser and client an special case that the underlying frameworks need to handle specifically without raising an exception.
Expected Behavior
When client (browser/javascript) drops connection, no exception is raised. E.g. Spring Boot does not raise any exception.
Actual Behavior
Possible Fix
Allow to configure to ignore "client connections aborts" for specific connections or detect context of the connection to handle client connection abort correctly.
Steps to Reproduce
Currently I'm trying to set up a simple project to reproduce the issue .. Is this issue maybe related to not correct WebFlux configuration as we use WebFlux together with Spring MVC?
Your Environment
- Version used: 2.14.0
- Link to your project: to follow ...
In order to prioritize the support for Logbook, we would like to check whether the old issues are still relevant.
This issue has not been updated for over six months.
- Please check if it is still relevant in latest version of the Logbook.
- If so, please add a descriptive comment to keep the issue open.
- Otherwise, the issue will automatically be closed after a week.
This issue has automatically been closed due to no activities. If the issue still exists in the latest version of the Logbook, please feel free to re-open it.