Ed Avis <[EMAIL PROTECTED]> writes:
> [EMAIL PROTECTED] (Andrew M. Bishop) writes:
>
> >>pressing reload in the web browser (Mozilla) doesn't cause wwwoffled
> >>to contact the server for a fresh version.
>
> >>+ request-changed = -1
> >
> >This would seem to be the one that is causing the problem. It says
> >that the page is not to be refetched when online.
>
> But I'm sure I always used to have that setting in the config file,
> and it gave the behaviour that the cached version would always be used
> _except_ when hitting the reload button in the browser. Doing an
> explicit reload would always cause wwwoffled to fetch a fresh copy.
>
> Is there a way I can get that behaviour with the current release?
WWWOFFLE doesn't know when you have pressed reload in the browser, it
only knows when the browser asks for a forced reload. In some
browsers these are the same thing and in some browsers they are not.
Personally I prefer a browser where pressing reload does not force a
refresh but just asks WWWOFFLE to decide. There also needs to be a
way of forcing a reload hence the use of shift-reload or
control-reload.
To work out exactly what is happening you need to run WWWOFFLE with
debugging enabled and see why it decides to give you the same page or
a new page.
--
Andrew.
----------------------------------------------------------------------
Andrew M. Bishop [EMAIL PROTECTED]
http://www.gedanken.demon.co.uk/
WWWOFFLE users page:
http://www.gedanken.demon.co.uk/wwwoffle/version-2.8/user.html
