commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 20838] - Add a new property maxFileSize to control a size of separate uploaded file but not a whole request
Date Fri, 20 Aug 2004 00:49:10 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=20838>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=20838

Add a new property maxFileSize to control a size of separate uploaded file but not a whole
request





------- Additional Comments From justin@armory.com  2004-08-20 00:49 -------
We've done something like this (in our own FileItem implementation).

In particular, we want to continue parsing the remaining items even if one item
is a huge file, so we implemented our own FileItem that contains an OutputStream
wrapper that keeps track of the file size but doesn't keep any data for a file
that is too big. Other parts of the system can then see that a file was
uploaded, along with its filename and even its size, but none of the data.

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message