> However, unfortunately, I couldn't find the answers to my questions in > there.
"If you have multiple users, you will probably want to disable the local interface by setting the variable disableLocalInterface. You may also selectively control setting of variables, indexing and listing known servers by setting the variables disableConfiguration, disableIndexing and disableServersList." While it doesn't explicitly say that the local interface is the union of the three, I think it's fairly clear. (Well-written patches to the documentation usually get applied straight away.) > Thanks for that. Although, what's the difference between the config > page and the main server? Surely there's no point in accessing the web > server without the config page? The web server is read-only, it's a convenient place to put Polipo's documentation, a proxy.pac file or anything that might be of interest to your users. The local interface allows changing the proxy's configuration as well as allowing your users to see the index of the cache. (It is none of your users' business what kind of political blogs you like to read, or what kind of naked people you like to look at.) > If this is set, though, is it correct that you can only access the web > interface by using one of the username:password combinations stored in > the config file? Why don't you try it yourself and send in a patch to the documentation? (The answer is yes.) -- Juliusz ------------------------------------------------------------------------------ Learn Windows Azure Live! Tuesday, Dec 13, 2011 Microsoft is holding a special Learn Windows Azure training event for developers. It will provide a great way to learn Windows Azure and what it provides. You can attend the event by watching it streamed LIVE online. Learn more at http://p.sf.net/sfu/ms-windowsazure _______________________________________________ Polipo-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/polipo-users
