Closed (won't fix)
Project:
Drupal core
Version:
x.y.z
Component:
node system
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
25 Nov 2003 at 00:40 UTC
Updated:
4 Dec 2003 at 06:57 UTC
One user of a Drupal site I recently configured writes:
At least under Safari, the pages seem to be being cached more aggressively than I would expect. This means one has to hit refresh to see changes more than I would have expected.
Comments
Comment #1
moshe weitzman commentedPlease include steps to reproduce this. Further, it would be nice to know more about your setup. Particularly note if user is logged in and whether you have caching enabled
If you can reproduce this at drupal.org, we should have all the info needed to fix it.
Comment #2
Eric Scouten commentedI just observed this bug using Safari on Mac OS 10.3.1. Here are steps to reproduce.
(1) View a book page that already exists.
(2) Edit the content of that page and submit your edits.
(3) Click on the "view" link to return to the book page.
(4) Look at the contents of the book page as rendered now.
Actual result:
Old content (prior to edit) is displayed. You have to refresh the page to get the new content.
Expected result:
New content you just submitted will be displayed.
Another CMS I've used in the past, TWiki (www.twiki.org), gets around this by adding a timestamp when you go back to view the page. (In other words, instead of /node/view/92, you get /node/view/92?timestamp=728394724.) The timestamp is ignored by TWiki, but causes the browser to think it's fetching a different page.
Another possibility is to add a meta refresh tag on the first page view after an edit.
Comment #3
Eric Scouten commentedThis occurs with a Drupal installation based on CVS as of about three weeks ago.
Comment #4
dries commentedLooks like Safari (or an intermediate proxy) is serving _locally_ cached pages. I'm tempted to say "Won't fix" because it sounds like a bug in their caching code, not ours. Do you have a pointer to the related TikiWiki thread? Have you check with the Safari project?
Comment #5
Eric Scouten commentedFair point. I cannot reproduce this bug on IE 6.0 on Windows, even with the "Check for newer version of stored pages" setting on "Automatic." (I would assume that this setting is IE's most aggressive setting for caching.)
I'll switch it to "won't fix" unless I come up with some evidence that Safari is behaving correctly.
Comment #6
Eric Scouten commentedSome Googling shows that this is in fact a known Safari bug. Sorry for the bother here. If anyone is interested, here is some discussion on the topic:
http://www.codepoetry.net/archives/2003/11/07/safari_and_ifmodifiedsince...