If the request isn't initiated by the browser to the server, then shouldn't this be a browser issue ?
On Sat, Oct 15, 2011 at 12:54 PM, ManuPK <manupk.t...@gmail.com> wrote: > I am using tapestry version 5.0.18. In my application the tapestry pages > are > getting cached. ie, when I hit the URL to load the page the request is not > reaching the server. I need to press ctrl+F5 to get the valid page. > > Is it because of the page pooling? Or how can I make sure always the > request > is reached the server and the fresh data is loaded to the page. > > -- > View this message in context: > http://tapestry.1045711.n5.nabble.com/Page-is-getting-cached-in-Tapestry-5-0-18-tp4905016p4905016.html > Sent from the Tapestry - User mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > -- *Regards,* *Muhammad Gelbana Java Developer*
