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 > > -- Pedro Henrique Oliveira dos Santos --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
