https://bz.apache.org/bugzilla/show_bug.cgi?id=58031
Bug ID: 58031
Summary: Posting data exceeding maxPostSize should result in
HTTP 413.
Product: Tomcat 9
Version: unspecified
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: P2
Component: Catalina
Assignee: [email protected]
Reporter: [email protected]
Created attachment 32821
--> https://bz.apache.org/bugzilla/attachment.cgi?id=32821&action=edit
Initial draft of patch to set status as 413 when maxPostSize is exceeded.
When data exceeding the value of the "maxPostSize" configuration parameter is
posted within a deployed application, the application sees an empty request
parameter map and cannot access the posted data, yet Tomcat returns a 200
status, indicating to the client that everything was processed successfully
(which likely will mislead the client). The correct behavior is to return a
status of 413 ("Request Entity Too Large") to indicate that the request could
not be fully processed due to the size being too large.
Attached is a patch that will set the response status to 413 when Tomcat
discovers that the posted data exceeds maxPostSize.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
