Re: File upload "too large" error managing

Hi, please create a quickstart and attach it to a new issue. It would be nice to be able to run it with Jetty. You can check any differences between your code and the file upload example in wicket-examples: the error message works fine there for your case (i.e. container limit > file size >

Re: [VOTE] Release Apache Wicket 6.28.0

+1 to release On Fri, Sep 29, 2017 at 9:41 AM, Martin Grigorov wrote: > +1 to release > > Martin Grigorov > Wicket Training and Consulting > https://twitter.com/mtgrigorov > > On Wed, Sep 27, 2017 at 10:22 PM, Sven Meier wrote: > > > +1 > > > > Thanks

Re: [VOTE] Release Apache Wicket 6.28.0

+1 to release Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Wed, Sep 27, 2017 at 10:22 PM, Sven Meier wrote: > +1 > > Thanks Andrea! > > Sven > > > > Am 27.09.2017 um 20:33 schrieb Tobias Soloschenko: > >> +1 >> >> Good to see the page store

Re: wicket 8.0.0 milestone tags in github?

Gitbox is just full access to Github. You can push there and it will be synch-ed with Apache Git automatically. You can merge PRs. I think some projects even use the Issues functionality instead of JIRA / Bugzilla. Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On

Re: File upload "too large" error managing

Hi, For Tomcat I'd recommend you to set maxSwallowSize to the connector: https://tomcat.apache.org/tomcat-8.5-doc/config/http.html Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Fri, Sep 29, 2017 at 10:22 AM, Andrea Patricelli < andrea.patrice...@tirasa.net>

Re: File upload "too large" error managing

Yes Emond, I guess that my error is the same, and your explanation is very convincing :) Is there a solution, i.e. to better control such error? Or, better, is it a bug? Best regards, Andrea Il 29/09/2017 08:44, Emond Papegaaij ha scritto: Hi, I've seen the error you describe before.

Re: File upload "too large" error managing

Hi, I've seen the error you describe before. It happened to me when a file- submitting ajax call fails when using a Content-Security-Policy. The problem is that an error is returned to the browser (in my case Chrome), which renders an error page inside the iframe used to submit files via ajax.