Open dunnl opened 7 years ago
(Changed the title because initially I thought requestSizeCheck was the problem)
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?