Re: [squid-users] Netscape to Squid conversion Issues

From: Henrik Nordstrom <henrik_at_henriknordstrom.net>
Date: Tue, 09 Dec 2008 22:51:30 +0100

tis 2008-12-09 klockan 15:03 +0100 skrev Jan Welker:

> A. Netscape browsers with manual proxy servers set up for http and
> https as proxy.host.net:8080
> B. Netscape browsers with automatic proxy configuration with URL setup
> as proxy.host.net:8080 (note they're the same).

Ugh..

This kind of setup isn't well supported by Squid at the moment, but
there is a workaround by enabling the transparent http_port option, and
then set up a small web server hosting the pac.

http_port 8080 transparent
cache_peer pac.server 80 0 no-query originserver name=pac
acl pac dstdomain proxy.host.net ip.of.proxy.host.net
cache_peer_access pac allow pac
never_direct allow pac

> to be touched). If I must do that, I'd much prefer to cut over to
> transparent proxying so we don't face this problem again in the future
> and it's trivial for the end users to reconfigure.

I wouldn't do that. Better to set up a "pac.host.net" address and
gradually migrate the clients over there so you get the pac distribution
separated from the actual proxy, enabling you to play with the proxy
hierarchy without touching the pac distribution (just the pac).

But the workaround above should get you going. If not it should be
fairly easy to add what's needed.

Regards
Henrik
Received on Tue Dec 09 2008 - 21:51:36 MST

This archive was generated by hypermail 2.2.0 : Wed Dec 10 2008 - 12:00:02 MST