ok I managed to get some hints from my browser. So Certain URL's rendered as http://<host>/null would cause 404 .. but the progressBar / Ajax related issue was caused due to something like this:
Not really in my hands .. so am just switching back to a simple HTML 404 rather than a dynamic one. I dont want to get into the whole business of filtering through the kind of 404 or origin of 404 nonsense. ..though if someone has any ideas , please am all ears. thank you. ----- 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/Setting-up-custom-404-page-causes-Issues-tp4659671p4659674.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
