"Paul A. Rombouts" <[EMAIL PROTECTED]> writes:
> The way I see it, the problem only occurs when *all* of the following conditions
> apply:
>
> - the browser doesn't have a copy of the page in its cache
> - WWWOFFLE does have a copy of the page in its cache
> - WWWOFFLE is online
> - WWWOFFLE is configured to (re-)request the page
> - the remote server responds with code 304 (not modified).
This is correct, but there is one additional condition:
- WWWOFFLE decides that it should ask if there is a newer page than
the one that is cached.
Saying that "WWWOFFLE is configured to (re-)request the page" is
certainly a condition for this, but there are many options that change
how WWWOFFLE re-requests pages. This is one of the important features
of WWWOFFLE for the users, the ability to reduce network traffic by
being more aggressive with caching.
If you are interested in how to configure WWWOFFLE to (not) re-request
pages then you should look at the following options:
request-changed = (time) (default=10m)
This configures WWWOFFLE to set the minimum time between
refetching a page that is already cached.
Increasing this number will increase the length of time that
pages stay in the WWWOFFLE cache and reduces bandwidth.
request-changed-once = yes | no (default=yes)
This configures WWWOFFLE to only fetch a page once in each
session online. This takes priority over the request-changed
option if it is enabled.
Enabling this will stop the same page or image being
downloaded more than once in a session.
request-expired = yes | no (default=no)
This option configures WWWOFFLE to re-fetch pages that have
expired. The expiry time is based on the headers that the
server sent back with the page last time. This option takes
priority over the request-changed and request-changed-once
options if it is enabled.
Enabling this option will mean that the WWWOFFLE cache and the
browser will be forced to update the page nuder the control of
the server. Expiry times can be used for good reasons (to
stop the display of data that becomes invalid after time) or
for bad reasons (to force browsers to reload adverts).
request-no-cache = yes | no (default=no)
This option configures WWWOFFLE to re-fetch pages that ask not
to be cached. The request not to be cached is contained in
the headers that the server sent back with the page. This
option takes priority over the request-changed and
request-changed-once options if it is enabled.
Enabling this option is similar to the request-expired option
except that a different set of server headers are examined.
All of these options can be specified on a URL by URL basis or to
apply to all URLs.
--
Andrew.
----------------------------------------------------------------------
Andrew M. Bishop [EMAIL PROTECTED]
http://www.gedanken.demon.co.uk/
WWWOFFLE users page:
http://www.gedanken.demon.co.uk/wwwoffle/version-2.7/user.html
