I figured it out, it wasn't a Wicket thing. Someone changed our script for setting up an application server in Eclipse WDT, making it ssl-only (secure cookie). So when I switched to https, everything worked fine.
Makes perfect sense, in hindsight, the page comes up in http, but no request can be serviced. So Wicket's not the blame, but it would have been nice to have had a simple error or warning on this, but I don't know if that is possible at all. Thanks to Martin and Ernesto for their replies. Regards, Hans -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/HomePage-reloads-on-every-Ajax-submit-tp4672412p4672438.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
