Andrew M. Bishop wrote: > > BTW, what is the "config" button at the end of the page for? Don't I have > > to run "update" first? > > To allow you to update the configuration file. Perhaps you edited > outside of the WWWOFFLE control page or something.
I mean the button at the end of http://localhost:8080/control/edit/. So pushing "config" makes wwwoffle write changes to the config file and re-read it? > I can change the code to allow max-size=-1 to mean "ignore the > option", but changing max-size=0 to mean "delete all the cached files" > will cause problems for some users. If people don't change the config > file then it will delete all of their cache. I just know that this > will cause problems. Yes, I see that problem. On the other hand, a script could change max-size=0 to max-size=-1 when updating from <= 2.7f. I find deleting all files useful if I know that there's a lot of junk in the cache. > Have you tried to fix your browser? Well, Konqueror 3 lets me specify whether to use a proxy and if the browser cache should be used, but there's nothing on pragma:no-cache. I fixed the problem with your advice to delete a line from the wwwoffle source. > The documentation in the README.CONF file makes it clear when you > should use the pragma-no-cache option. ...when all pages are re-requested by a 'broken' browser. Maybe Konqueror is even more broken. I'll send a report to the kde-bug-list. > An option called rerequest-cached-pages is ambiguous because it might > mean that you should re-request all cached pages all the time. What > you actually want is re-request-cached-pages-when-the-browser-asks or > something. Maybe ignore-browser-rerequests # yes: prevent 'broken' browser from re-requesting cached pages while browsing offline in the offline section? > This is because recursive fetching is performed in the background. It > might take a long time and behaves differently online and offline. When it is online and has finished fetching, could it display a message? Otherwise, users that don't have modems with LEDs on it may not know when fetching is over. > > 7. wwwoffle should go online before fetching if it is offline. > > There are separate options for online and fetching. It is not > expected that 'wwwoffle -online/-offline/-fetch' will be run manually, > but will be used in automatic scripts. In this case there is no > problem with running the program twice. I see. Then I have a different suggestion: add a link from http://localhost:8080/control/ to http://localhost:8080/index/outgoing or some other cache index. I think control, cache and config are the pages you need most often. > The FAQ is for WWWOFFLE questions while the files in the contrib > directory are not part of WWWOFFLE, they are just things that people > might find useful. If the documentation in contrib/README is not > enough then I can remove the wwwoffled.rc script that you have > problems with. The redhat script didn't work on my system, I remember it had some wrong links. I set up another script that should work if wwwoffle is installed from tarball. I can send you that script, together with a Readme on how to install it. I certainly don't want to bash wwwoffle, it's a good and powerful program. But I believe that some things could be streamlined to make it easier to use. Cheers, Boris
