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 27328] - tie content length of form fields posted with struts-validator maxlength attribute or alike
Date Sun, 17 Oct 2004 06:27:17 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=27328>.
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=27328

tie content length of form fields posted with struts-validator maxlength attribute or alike





------- Additional Comments From hauser@acm.org  2004-10-17 06:27 -------
Martin, 
As per your note on unstoppability, you are saying if somebody tries to kill my
server by uploading an excessively large file, FileUpload has no way to preempt
that before throwing an out-of-memory exception and leaving the JVM in a
non-determined state?

What I orignially tried is to leverage the "safe operations parameters" that
programmers increasingly specify via the validator.xml in a declarative way.

It would be great if an upload would stop or at least avoid OOME driven by some
parameters (best if there is only one set of such parameters - e.g. the same as
the ones from struts cited above).

This idea is basically related to Bug 22633.

---------------------------------------------------------------------
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