Hi, I just encountered a strange problem using Safari while browsing on a Wicket application. The thing is, Safari seems to cache all possible pages as hell. When pressing on a back button, I went back to a url like http://localhost:8080/testapp/?path=83 but this page wasn't the previous page but a page which has been cached a lot longer ago but was mounted as ?path=83 as well. When pressing reload, the correct page was reloaded from Wicket. I think this is very strange and I can't explain why the previous page was not in cache while a page which was a lot older was... Anybody encountered something like this as well?
Ralf ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_idv37&alloc_id865&op=click _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
