avoiding browser chache when velocity templates are used?
943348Jun 13 2012 — edited Jun 13 2012We have separate velocity templates for each page.Then to render a page, we will get the merged vm template as a string and then flush to a jsp.
The issue is we need to eliminate browser chaching for few pages.We have added the following codes both in the flushed jsp and vm template.But
the content is still browser cached and this isue is happening for windows XP and not with other OS.We need to eradicate this issue as XP is mostly used.
Added
$response.setHeader("Expires", "Mon, 23 Aug 1982 12:00:00 GMT")
$response.setHeader("Cache-Control", "no-store, no-cache, must-revalidate")
$response.addHeader("Cache-Control", "post-check=0, pre-check=0")
$response.setHeader("Pragma", "no-cache")
inside Head tag of all velocity templates. And response obj is added to context map. Added the same snippet in jsp.
Also added the <Meta> tag in all velocity templates as
<META HTTP-EQUIV="Cache-control" CONTENT="no-cache">
<META HTTP-EQUIV="Pragma" CONTENT="no-cache">
<META HTTP-EQUIV="Expires" CONTENT="0">
Still the issue persists.
Suggestions/solutions needed in this regard.