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
requestSizeCheck modifies a request to embed size-checking inside the responseBody instead of performing the check immediately. (And I presume this is on purpose.)
My concern is the error handling suggests that the exception could be thrown at this line in handleRequest' but I don't think makeActionEnvironment forces the evaluation of the request body either. If it does though, then getErrorHandler config status413 is fed into respStateToResponse, which throw an error.
Thoughts?
The text was updated successfully, but these errors were encountered:
dunnl
changed the title
requestSizeCheck too lazy?
Limiting the request size
Mar 1, 2017
The size check will be executed when the body is actually consumed and that's when the exception will trigger. It seems that you are correct that the exception will never be thrown at the line you mentioned. This was the case before as we already parsed the body there strictly before actually needing it. I guess one could remove the handler there.
requestSizeCheck modifies a request to embed size-checking inside the
responseBody
instead of performing the check immediately. (And I presume this is on purpose.)My concern is the error handling suggests that the exception could be thrown at this line in
handleRequest'
but I don't thinkmakeActionEnvironment
forces the evaluation of the request body either. If it does though, thengetErrorHandler config status413
is fed intorespStateToResponse
, which throw an error.Thoughts?
The text was updated successfully, but these errors were encountered: