In message <_A4726@delegate-en.ML_> on 01/14/10(19:25:34)
you Stefan Demmig <email@example.com> wrote:
|I have got another point to discuss. I wonder if I completely understud the EXPIRE process. in my parameter list
|arg CRON=30 0 * * 1-5 -expire 30d
|I wanted the system to expire files after 1 day and to delete expired files
|after 30 days so that after 31 days of no trafic the cache would be empty again.
|Is the parameter pair 10 + 11 correct and will it work under Windows?
Sorry but I've not tested "CRON ... -expire" enough especially
|What happens, if a file on a web server changes before 1 day. Will I receive the
|cached file or will it be reloaded from the original server, since it changed?
The EXPIRE=xxx parameter makes DeleGate reuse cached data anyway
while the age of a cahced data is newer than xxx, by default.
But clients (browsers) can override this behavior by indicating
forced "reload" or "veriry" a cached data as supported (with Pragma
or Cache-Control header in the HTTP protocol).
In a typical implementation of a browser, reloading will cause
verifiation of freshness, and if it modified after the time of
the cache, the latest version will be downloaded (and cached).
|If I normally receive the cached version of the file, I should keep the cache
|period as small as possible. There might exist a mechanism which checks if the
|cached file is still up to date (some time&date data from the original server)
|and if not so reloads the file. The cached file will be removed if not accessed
|by any client for a certain period of time e.g. 1 month.
9 9 Yutaka Sato <firstname.lastname@example.org> http://delegate.org/y.sato/
( ~ ) National Institute of Advanced Industrial Science and Technology
_< >_ 1-1-4 Umezono, Tsukuba, Ibaraki, 305-8568 Japan
Do the more with the less -- B. Fuller