mi <[EMAIL PROTECTED]> writes:
> There could be RAM caching involved, at least in some cases.
> I set 'disk cache' to 0, but how about the RAM ?
> Example:
> If i change a local page with an editor, and click on the same link
> or type in the same location in the browser address field, no
> changes are shown.
> Even not when i visited some other URL inbetween.
> I have to use the reload button or ctrl-r to update the browser view correctly.
This sounds like there is RAM or disk caching by the browser so that
it does not always reload the latest version. You can reduce this by
reducing the size of the browser's disk cache, try setting it very
small.
> I can't even guess if this is something browser specific or rather a
> filesystem/kernel feature.
> It's a 2.4.26 here, rootsystem and wwwoffle-cache are ext2.
> Browser is galeon. The same with firefox. But they both are close to mozilla.
I think that it is a browser feature.
> > > How can i get the 'confirm-reuest = yes' feature without problems ?
> > I don't know. I can reproduce it here with confirm-requests=yes.
> > If you want to refresh the page you need to confirm it, if you don't
> > want it then don't confirm it and don't press refresh again.
>
> With the RAM reload and the wwwoffle confirm=yes,
> working with logins, webforms and editing content management systems (like wikis)
> is unreliable and sometimes dragged me crazy.
> I saved my soul with a second browser which connects directly to the net,
> and which i use for editing. But there should be a solution with wwwoffle and
> confirm=yes altogether.
You can configure WWWOFFLE not to need a confirmation for the pages
that are causing you a problem.
--
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
