Re: Setting the cache control in the component

2016-07-07 Thread g kuczera
Hi guys, The problem was solved by setting the headers via the instance of the Response class (in the setupRender method), like this: response.setHeader("Cache-Control", "no-cache,no-store,must-revalidate"); response.setHeader("Pragma", "no-cache"); response.setHeader("Expires", "-1"); 2016-07

Re: Setting the cache control in the component

2016-07-05 Thread g kuczera
PS: I don't think that this is a Tapestry related issue, but I would like to hear your opinion. A also tried to add the pragma value - and it does not seem to change the way the website behaves (thou it appears in the page source). 2016-07-05 11:33 GMT+02:00 g kuczera : > Hi guys, > I wond

Setting the cache control in the component

2016-07-05 Thread g kuczera
Hi guys, I wonder how to prevent from returning to the previously visited page (the specific one, with important content). I figured out, that there is a cache-control header, which forces the web browser to load the page from the server again. That would be fine, but after setting the cache-contro