Re: Pressing reload in browser still uses cached page

amb-Uxr6IM1mbv2TY6FTCsQk+9Bc4/[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?

>There are two things that pressing reload in a browser can do.  it
>can either ask the proxy for another copy of the same page or demand
>that the proxy get a new version of the same page.  I don't know what
>browser you are using, but it seems that it is only asking for a new
>page and not demanding that one is fetched.

I'm using Mozilla/1.7, I also use Dillo and I think I saw the same
behaviour there.  That is, until recently Reload used to get a fresh
copy, but now it just shows the copy from the cache.

>You could try holding shift or control when pressing reload to see if
>it forces the reload.

I'll try that.

-- 
Ed Avis <[email protected]>