Dan Jacobson <[EMAIL PROTECTED]> writes: > >>>>> "R" == Roland Rosenfeld <[EMAIL PROTECTED]> writes: > > R> On Thu, 22 Aug 2002, Dan Jacobson wrote: > >> Package: privoxy > >> Version: 2.9.14-beta-2 > > >> I use wwwoffle. > >> After every connection to the web > >> $ wwwoffle-ls lasttime > >> shows that http://config.privoxy.org/send-stylesheet > >> has been gotten again. Erie. Like it is seeing how many users it has > >> or something. > > R> First question as always is you stacked privoxy and wwwoffle. Does > R> the browser ask privoxy and privoxy asks wwwoffle or do you use the > R> reverse way? > > well, in my wwwoffle conf file > Proxy > { > <http://*> proxy = localhost:8118 > } > so the latter. > > R> The first variant shouldn't cause trouble, while the second one does, > R> because you cannot configure wwwoffle to handle the requests to > R> config.privoxy.org and p.p directly instead of caching or delaying > R> them. > > OK, interesting. I'll cc this to the wwwoffle list. Hmmm, maybe one > can configure privoxy itself to more efficiently treat such > requests...
I think that the biggest problem with privoxy and WWWOFFLE is that the privoxy configuration URLs are only accessible if you use privoxy as a proxy. (This is my understanding from two privoxy+WWWOFFLE users anyway). With WWWOFFLE you configure it as a proxy on port 8080 on localhost. You can access the WWWOFFLE internal configuration URLs using the URL http://localhost:8080/, this URL does not need to go through the WWWOFFLE proxy. It works equally well if there is no proxy configured in the browser. With privoxy you need to access URLs like http://config.privoxy.org/, using privoxy as a proxy, to configure it. This is why people keep asking me to allow WWWOFFLE to use proxies when offline. There is apparently no way to access the privoxy configuration URLs without using privoxy as a proxy. This means that if you chain proxies and use WWWOFFLE closest to the browser then WWWOFFLE must still act as a proxy to hosts that are not localhost even when offline. If privoxy accepted the URL http://localhost:8118/ (for Dan's configuration above) as a URL to configure it then there would be no problem, it would be proxied by WWWOFFLE all the time and never cached. -- Andrew. ---------------------------------------------------------------------- Andrew M. Bishop [EMAIL PROTECTED] http://www.gedanken.demon.co.uk/ WWWOFFLE users page: http://www.gedanken.demon.co.uk/wwwoffle/version-2.7/user.html
