https://bz.apache.org/bugzilla/show_bug.cgi?id=58031
--- Comment #1 from Christopher Schultz <ch...@christopherschultz.net> --- I'm iffy on this patch because it's not configurable (I'd like to point out that the current behavior is also not configurable, and this definitely is an improvement). The application itself might want to check this situation and react differently, like it can when there are too many request parameters. You should check out the FailedRequestFilter to see what happens in that case: http://tomcat.apache.org/tomcat-8.0-doc/config/filter.html#Failed_Request_Filter It does almost what you want, except that it returns a 400 response instead of 413, and only currently works for violations of maxParameterCount. Look into how Globals.PARAMETER_PARSE_FAILED_ATTR is used to communicate this situation to the application and see if you can come up with something that might work better than your current proposal. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
