Hi Martin, > The maximum size configuration has nothing to do with memory > usage. In the > default implementation, the entire upload is almost never retained in > memory, unless it is very small. Once it passes a > configurable threshold, it > is written to disk instead.
Doesn't disk writing introduced new weaknesses? PHP does it similar it copies a file into the tmp directory of the server. So developers have to move the file localy. Is this simlilar implemented in FileUpload? > > The main reason for the maximum size configuration is so that > clients are > constrained in how much data they can send to the server, > which also helps > to prevent DoS attacks. Do you really want some random hacker > uploading a > 100GB file to your web server? ;-) Good point so I really understand what the max size configuration is for. :-) Do I have to increase JVM max memory when i would allow let's say 200MB? What does the interally byte buffer consume? Bye and Thx Toby --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
