Website 'recent posts' section reloads on 'back'

Same for me. On Safari on 10.4.6 I don't see a reload. Even if I did I'm not sure what I would do about it being the inept web programmer that I am :)

"Not Camino's fault; Safari shouldn't be caching it either.

curl -I http://www.hogbaysoftware.com/tracker
HTTP/1.1 200 OK
Date: Thu, 11 May 2006 16:22:01 GMT
Server: Apache/2.0.54 (Unix) PHP/4.4.2 mod_ssl/2.0.54 OpenSSL/0.9.7e
mod_fastcgi/2.4.2 DAV/2 SVN/1.1.4
X-Powered-By: PHP/4.4.2
Expires: Sun, 19 Nov 1978 05:00:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Set-Cookie: PHPSESSID=47de30a845b049bbf418bbc94ae962f5; expires=Saturday,
03-Jun-06 19:55:21 GMT; path=/
Last-Modified: Thu, 11 May 2006 16:22:01 GMT
Vary: Accept-Encoding
Content-Type: text/html; charset=utf-8


"If you note where it says "no-cache", the site (or Apache
rather) is telling browsers not to cache the page. Camino (and I assume
Firefox) honors this."

----

Jesse - do you think you could go in and change the Cache-Control setting? It really slows the site down for browsers (like Camino and Firefox) that respect that setting.

(Here's the link to the Bugzilla report.)

I'm not sure if there is anything I can easily do about this. I already have caching turned on, but it seems drupal will only cache for "anonymous" users, for registered users it always queries the database. At some point (once it has an official release) i'll probably start using drupal's new "Views" module. That will replace the tracker page, allow for better RSS feeds, and I think maybe provide better caching support. So I guess caching is another reason to upgrade to the views module as soon as possible.

Interesting - thanks for looking into this. The other side-effect of the always-query mode I forgot to mention is that my position in the previous page is forgotten when I use 'back'. So for example, if I'm far down into the tracker page and click on a post and hit 'back', I'll be taken to the top of the tracker page. Thanks again for looking for solutions in the future versions of drupal modules.