Re: Re: confused reloading of pages

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.

I made a funny experiment.
I pointed the browser to http://woody (my localhost).
Then i modified the local apache documentroot index.
Then i pointed the local browser to http://localhost -> All modifications are shown.
Then i recalled http://woody by address field -> No modifications visible.

Apparently reloading a (local) page 'normally' (not via the reload button) does restore from RAM.

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.
How about other browsers ? Konqueror ? Links ?

> > 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.


-- 
Michel...

















.