You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I recently stumbled across this observation with the timeout middleware:
If a client makes a request, but closes the connection before the server has a chance to respond, the timeout still expires after the allotted amount of time, and an error occurs.
For the sake of preventing irrelevant errors from being populated in log files, I'm wondering if request timeouts should be cleared if the connection is closed. For the time-being I've added the following before the 'timeout' middleware.
Hi! There is no source for timeout middleware in here, so there is nothing that can be done in this project. Please file the issue at connect-timeout library. Also, yes, it should be cleared.
I recently stumbled across this observation with the timeout middleware:
If a client makes a request, but closes the connection before the server has a chance to respond, the timeout still expires after the allotted amount of time, and an error occurs.
For the sake of preventing irrelevant errors from being populated in log files, I'm wondering if request timeouts should be cleared if the connection is closed. For the time-being I've added the following before the 'timeout' middleware.
The text was updated successfully, but these errors were encountered: