You can setup a firewall to prevent DOS attacks, I'm not sure if Wicket needs to read the input stream regardless of its HTTP header specifying that the upload exceed the limit just to close the stream.
On Thu, May 12, 2011 at 1:52 PM, Phil Franken <phil.fran...@gmail.com> wrote: > Thanks for the update Pedro. I concur with your assesment based on what > I've seen, but this makes me worry. Does this mean if I set a file size > limit of 1MB and someone uploads a 2GB file the container will read the > entire 2GB? Not good, with or without progress bar. Anyone suggestions on > how to handle this? > > On 5/12/2011 7:47 AM, Pedro Santos wrote: >> >> Hi Phil, I'm about to upload a quickstart to this ticket proving it is >> not a Wicket related problem. The container is always reading the >> entire input stream regardless of the application doing it or not. >> I talked about in IRC and Igor suggested me to close the stream if it >> exceed the max limit, but by doing so the client gets no response and >> browser shows a page saying that the connection to server are lost. >> >> >> On Thu, May 12, 2011 at 3:39 AM, Phil Franken<phil.fran...@gmail.com> >> wrote: >>> >>> Are there any plans to include a fix for this in 1.14.18? >>> >>> https://issues.apache.org/jira/browse/WICKET-3594 >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >>> For additional commands, e-mail: users-h...@wicket.apache.org >>> >>> >> >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > -- Pedro Henrique Oliveira dos Santos --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
