Aren't you sending your data in the url? Even if you are using POST you can still have some (all) data in the url as query parameters. And there are limits for url length (both on client/browser side and server side). This would also explain why does it depend on header buffer size as the url is read into that buffer.
Attila 2011/9/25 Arjun Dhar <dhar...@yahoo.com> > Since it was a server error, I changed the "headerBufferSize" config in > Jetty > and it worked > ..but then on changing Jetty Config wicketAjaxPost & wicketAjaxGet were > both > working. > > "headerBufferSize" uses the request header imo, so on post why do we need > the request header? > ..Something does not seem right with my understanding of these functions or > perhaps how JETTY handles requests. > > Its left me a little confused :( > > > Jetty config fix > -------------- > > <connector > implementation="org.mortbay.jetty.nio.SelectChannelConnector"> > > <port>9090</port> > > <maxIdleTime>60000</maxIdleTime> > > <headerBufferSize>24000</headerBufferSize> > </connector> > > > > ..what im still worried about is the HeaderBuffer Size > > ----- > Software documentation is like sex: when it is good, it is very, very good; > and when it is bad, it is still better than nothing! > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/wicketAjaxGet-Size-limt-tp3841117p3842018.html > Sent from the Users forum mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
