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
a client (either malicious or buggy) could easily consume a thread per each connection by sending a request with a body that exceeds :request-buffer-size slowly enough (or just pausing forever). In such a case we invoke handler on a response-executor before the body is read, meaning that call to bs/to-string effectively blocks a thread allocated.
The text was updated successfully, but these errors were encountered:
This could be done manually by switching to
raw-handler
and tracking time we need to read chunks from the stream, but in most general use case likea client (either malicious or buggy) could easily consume a thread per each connection by sending a request with a body that exceeds
:request-buffer-size
slowly enough (or just pausing forever). In such a case we invokehandler
on aresponse-executor
before the body is read, meaning that call tobs/to-string
effectively blocks a thread allocated.The text was updated successfully, but these errors were encountered: