Hi Phil, I replied in the ticket. Just realize it is not the right
thread to talk about.
On Thu, May 12, 2011 at 2:10 PM, Phil Franken wrote:
> Firewall not really an option (no budget). Ok so instead of closing the
> stream can you at least make sure the progress bar is invisible and let the
>
Firewall not really an option (no budget). Ok so instead of closing the
stream can you at least make sure the progress bar is invisible and let
the container do its thing? I'm using Tomcat do you know of any way to
set a max file size in Tomcat?
On 5/12/2011 1:02 PM, Pedro Santos wrote:
Yo
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 wrote:
> Thanks for the update Pedro. I concur
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 h
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
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.
Hello,
Following the release this morning of wicket 1.5-RC4.2 I have built and
deployed a matching wicketstuff-core 1.5-RC4.2 release.
The artifacts have been promoted and synced into the maven central
repository.
They can be retrieved like this:
org.wicketstuff
wicket-security-swarm
1.5-
