Re: Automatic proxy configuration
* Patrick Winnertz <patrick.winnertz@skolelinux.org> [070209 20:14]:
> Am Freitag, den 09.02.2007, 20:19 +0100 schrieb RalfGesellensetter:
> > Am Freitag 09 Februar 2007 19:20 schrieb Patrick Winnertz:
> > > I think it will do no harm if we use this automatic configuration
> > > script.
> > > Browsers which use the env vars, will use them, browsers which
> > > doesn't know about them will look for this script. everything will
> > > work out of the box ;-) and i think this is what we want.
> >
> > Hi Patrick,
> >
> > great. Just a thing to remember: If you happen to have configured your
> > proxy the right way, then there are other issues you have to fight:
> >
> > You have to define some exclusions to the rule because squid on webcache
> > fails to serve requests to tjener (I think) or to its webmin interface
> > (port 10000).
> Webmin will not be there in etch ;-)
> But of course you are right, there have to be exceptions for using the
> proxy
tjener, tjener.intern
>
> > If this is not possible with wpad, then we could try to
it is possible
http://wp.netscape.com/eng/mozilla/2.0/relnotes/demo/proxy-live.html
> > make squid to allow access to localhost/tjener. At this point, we might
> > want to do some more optimizations for squid configuration:
> > - prepare roomwise access control
> > - disable caching of pages whose caching is useless (volatile pages, big
> > files, ...)
> >
> > --> http://www.faqs.org/docs/securing/chap28sec235.html
> > --> http://wiki.squid-cache.org/SquidFaq/CacheManager
> Greetings
> Patrick
>
> >
> > Regards
> > Ralf
> >
Regards/AmicaLinuxement/Viele Gruesse!
Kurt Gramlich
--
kurt@skolelinux.de
GnuPG Key ID 0xE263FCD4
http://www.skolelinux.de
Reply to: