|Anonymous | Login | Signup for a new account||08-05-2020 00:06 PDT|
|Main | My View | View Issues | Change Log | Docs|
|Viewing Issue Advanced Details [ Jump to Notes ]||[ View Simple ] [ Issue History ] [ Print ]|
|ID||Category||Severity||Reproducibility||Date Submitted||Last Update|
|0004638||[Resin]||minor||always||06-22-11 10:56||06-28-11 11:14|
|ETA||none||Fixed in Version||4.0.20||Product Version||3.1.6|
|Summary||0004638: multipart-mime with length limit|
(rep by Daniel Kador)
I think there?s one more thing we need before we can put this issue to rest. Resin automatically stores the non-binary parts of multipart requests in memory. If somebody sends us a very large request, we could OOM. I?d like to have a parameter we can control that will determine the max allowed size of a non-binary part. If the size is over said limit, throw an IOException and fill in the ?caucho.multipart.form.error? request attribute with what went wrong.
Is that feasible? Let me know if I missed an option that already exists to control this behavior.
|Steps To Reproduce|
|06-22-11 10:56||ferg||New Issue|
|06-28-11 11:14||ferg||Note Added: 0005337|
|06-28-11 11:14||ferg||Assigned To||=> ferg|
|06-28-11 11:14||ferg||Status||new => closed|
|06-28-11 11:14||ferg||Resolution||open => fixed|
|06-28-11 11:14||ferg||Fixed in Version||=> 4.0.20|
| Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
28 total queries executed.|
25 unique queries executed.