You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tomcat.apache.org by bu...@apache.org on 2018/02/03 20:23:45 UTC

[Bug 62058] When file size exceeded in @MultipartConfig, Tomcat returns 500.

https://bz.apache.org/bugzilla/show_bug.cgi?id=62058

Mark Thomas <ma...@apache.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 OS|                            |All
         Resolution|---                         |WONTFIX
             Status|NEW                         |RESOLVED

--- Comment #1 from Mark Thomas <ma...@apache.org> ---
We can't fix this.

Parsing the parts is triggered by application code. Tomcat has no control over
how application code chooses to handle an error condition. Note that failure to
handle an error condition (i.e. catch the exception) will result in Tomcat
returning a 500 code.

The API that triggers parsing of the parts does not permit any checked
exceptions to be thrown to Tomcat has no choice but to use an unchecked
exception to handle the error.

Tomcat simply has not way to determine how the application wants to handle the
upload failure and therefore does not set any response code. That is an
application responsibility.

-- 
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org