| Anonymous | Login | Signup for a new account | 11-03-2025 20:55 PST | 
| 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 | ||||
| Reporter | ferg | View Status | public | ||||||
| Assigned To | ferg | ||||||||
| Priority | normal | Resolution | fixed | Platform | |||||
| Status | closed | OS | |||||||
| Projection | none | OS Version | |||||||
| ETA | none | Fixed in Version | 4.0.20 | Product Version | 3.1.6 | ||||
| Product Build | |||||||||
| Summary | 0004638: multipart-mime with length limit | ||||||||
| Description | 
		(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 | |||||||||
| Additional Information | |||||||||
| Attached Files | |||||||||
| 
 | 
|||||||||
| 	Mantis 1.0.0rc3[^]
	Copyright © 2000 - 2005 Mantis Group
	28 total queries executed. 25 unique queries executed.  |