On 2/10/2011 6:04 AM, Rainer Jung wrote:
Servlet 3 standardizes file uploads. It contains the ability to limit on request size, pretty much the same as commons fileupload
supported for many years.
It seems when this conditions triggers the rest of the request inout stream is still drained at the end of the request. swallowInput is
not being set to false.
It seems there's still no server-side prevention against huge uploads possible. The upload is not put into memory, but the thread is only
freed once the whole request body is read. Shouldn't Tomcat ignore the rest of data and close the connection in this case?
standard soTimeout (read timeout) should apply. Meaning, if the client stops sending data, it should eventually result in an IOException and
back out the thread.
Filip
Regards,
Rainer
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 10.0.1204 / Virus Database: 1435/3434 - Release Date: 02/10/11
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
