i think 10ms ajax ping to the server is too often. your server probably takes more then 10ms to generate a response so you will get all these ajax requests queue up... use a more reasonable duration, like 1 second.
-igor On Wed, Feb 3, 2010 at 5:12 AM, Tomasz Dziurko <tdziu...@gmail.com> wrote: > I have problem with page heavily using ajax and error 403 returned by > ajax response. > > There are 4 components on the page which are shown only for specific > period of time. I use AbstractAjaxTimerBehavior (duration 10ms) which > is calculating current phase and then according to this phase I make > some components visible and others invisible (user has limited time to > answer question and after it ends he's redirected to next question). > > Sometimes this page stops responding to any user clicks. After running > this application in debug mode I noticed that among many ajax info > messages I get one error: > > ERROR: Received Ajax response with code: 403 > > Is this related to Wicket or I should talk with my server provider to > check if he doesn't block ajax requests that come too often? > I am using Wicket 1.3.7 > > Thank you in advance for any help. > > -- > Regards > Tomasz Dziurko > > --------------------------------------------------------------------- > 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
