From bcb4bcc0173a048138920792627ed290c84e5bfe Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Sat, 9 Apr 2011 19:26:56 -0400 Subject: response --- ...lways_displayed__59___need_page_refresh_to_appear.mdwn | 15 +++++++++++++++ 1 file changed, 15 insertions(+) (limited to 'doc/bugs/New_comments_are_not_always_displayed__59___need_page_refresh_to_appear.mdwn') diff --git a/doc/bugs/New_comments_are_not_always_displayed__59___need_page_refresh_to_appear.mdwn b/doc/bugs/New_comments_are_not_always_displayed__59___need_page_refresh_to_appear.mdwn index 4a017857f..ac079f5b8 100644 --- a/doc/bugs/New_comments_are_not_always_displayed__59___need_page_refresh_to_appear.mdwn +++ b/doc/bugs/New_comments_are_not_always_displayed__59___need_page_refresh_to_appear.mdwn @@ -18,3 +18,18 @@ My assumption is that ikiwiki does not tell Chrome to reload the page as the cac Richard + +> There is some lurking bug with certian web browsers, web servers, or +> combination of the two that makes modifications to html files not +> always be noticed by web browsers. See +> [[bugs/firefox_doesn__39__t_want_to_load_updated_pages_at_ikiwiki.info]] +> see also . +> +> On Branchable, we work around this problem with an apache configuration: +> «ExpiresByType text/html "access plus 0 seconds"» +> +> There seems to be no way to work around it in ikiwiki's generated html, +> aside from using the cache-control setting that is not allowed in html5. +> +> And, which browsers/web servers have the problem, and where the bug is, +> seems very hard to pin down. --[[Joey]] -- cgit v1.2.3