On Sun, 14 Dec 2003, Tom Lisjac wrote:
I've written a small, Dillo friendly wiki/cms system in php that I'm hoping to release in a few weeks. During testing (today's cvs), I found that Dillo's cache wasn't expiring the dynamic pages. Here's the header I was initially using to disable client caching:
header("Expires: Sun, 22 Mar 1998 20:00:00 GMT"); header("Last-Modified: " . gmdate("D, d M Y H:i:s") . " GMT"); header("Pragma: no-cache"); header("Cache-Control: post-check=0, pre-check=0");
With this header, Dillo's stdout messages reported "bad clocks"... so I tried sending the same date for Expires and Last-Modified. Dillo's stdout came back with: "Forcing min expire 60 on >the url< instead 0". What does that mean?
you're using my patch? (it remainds, that i should try to clean up the cache patch for Jorge... oh well it's not easy work, i'm afraid...) Bad clocks means that the expiration time seems to be in history (compared to Last-Modified, when this header is present) for dillo at the time when the header was received, and is so more than 1000 seconds. These expirations are ignored, because many sites send these for all their content and it would otherwise cause dillo to always reload everything on these sites. For you're example - 1998 is very long history. Forcing min expire 60 - this is configurable using min_page_expire option in dillorc. When this config option is non-zero, dillo will set expiration times below this value (in seconds) to the config option value. It was introduced to give better speed with stupid news sites.
I really need the content of certain pages to expire immediately when viewed. Any suggestions for the correct header parameters would be greatly appreciated.
1. following dillorc options make it most agressivily reload everything: query_expire_time="0" min_page_expire="0" min_image_expire="0" 2. Use Cache-Control header: Cache-Control: no-cache