I noticed this evening that when a page is expired, if we make an Ajax
call from this page (autocomplete for example), the Ajax call returns
a 302 and then the entire page content (and not a valid XML Ajax
response) - I investigated it with Firebug as there's no error

Could it be related to WICKET-4454 ? We upgraded to 1.5.6 a few days ago.

It might be that I never waited long enough to see the problem before
but I'm pretty sure it was working correctly in previous versions.

Thanks for your feedback.


To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Reply via email to