aboutsummaryrefslogtreecommitdiff
path: root/templates/page.tmpl
diff options
context:
space:
mode:
authorJoey Hess <joey@gnu.kitenet.net>2010-03-31 17:51:46 -0400
committerJoey Hess <joey@gnu.kitenet.net>2010-03-31 17:52:58 -0400
commit4dcea6207d03fcdc25bc1c172d69c30673b7254a (patch)
tree0dd0dbfaa4f4e3c19ac8730dd6fa5aced3db179f /templates/page.tmpl
parentfc5445b90677489642e4ae8d5b2f6c54cdd847c5 (diff)
downloadikiwiki-4dcea6207d03fcdc25bc1c172d69c30673b7254a.tar
ikiwiki-4dcea6207d03fcdc25bc1c172d69c30673b7254a.tar.gz
page.tmpl: Add Cache-Control must-revalidate to ensure that users (especially of Firefox) see fresh page content.
Since Firefox version 3, it's done aggressive caching of visited pages, and does not, by default, check if the cached content is still valid when reloading or revisiting a page. By default, Firefox seems to not re-contact the web server at all. Compare with eg, Epiphany and Chromium, which appear to always check, and get back a 304 when the page is unchanged. This header makes Firefox do the right thing, at least for html files. It still over-caches if css, javascript, images, etc, are changed.
Diffstat (limited to 'templates/page.tmpl')
-rw-r--r--templates/page.tmpl1
1 files changed, 1 insertions, 0 deletions
diff --git a/templates/page.tmpl b/templates/page.tmpl
index 968066a19..c24f88823 100644
--- a/templates/page.tmpl
+++ b/templates/page.tmpl
@@ -3,6 +3,7 @@
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+<meta http-equiv="Cache-Control" content="must-revalidate" />
<title><TMPL_VAR TITLE></title>
<TMPL_IF NAME="FAVICON">
<link rel="icon" href="<TMPL_VAR BASEURL><TMPL_VAR FAVICON>" type="image/x-icon" />