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

http_port 192.168.0.15:8080 accel defaultsite=fu.company.com
cache_peer 172.0.0.1 parent 8080 0 no-query originserver

Your pointing it to its loopback address on port 8080, that would still be squid, you need to change that to the IP Address and port of the web server. You can run the web server on the same host if you like but it would have to be on a different port. Also I noticed in the earlier message that your auto configuration script isn't called out on the line if its http://proxy.host.net:8080/proxy.pac, and you are only specifying http://proxy.host.net:8080, you would need to make sure the web server is set to use proxy.pac as the default index page.

I hope this is a proof of concept test configuration, because if you have 6,000 clients 1g of cache really isn't going to help you very much.

Thanks,
     Dean Weimer
     Network Administrator
     Orscheln Management Co

-----Original Message-----
From: Jan Welker [mailto:jan.welker_at_gmail.com]
Sent: Tuesday, December 09, 2008 10:27 AM
To: squid-users_at_squid-cache.org
Subject: Re: [squid-users] Netscape to Squid conversion Issues

I am using Squid 2.6STABLE18.

My config:

acl all src 0.0.0.0/0.0.0.0

acl manager proto cache_object
acl localhost src 127.0.0.1/255.255.255.255
acl to_localhost dst 127.0.0.0/8
acl SSL_ports port 443 8443 # https
acl SSL_ports port 563 # snews
acl SSL_ports port 873 # rsync
acl Safe_ports port 80 # http
acl Safe_ports port 21 # ftp
acl Safe_ports port 443 # https
acl Safe_ports port 70 # gopher
acl Safe_ports port 210 # wais
acl Safe_ports port 1025-65535 # unregistered ports
acl Safe_ports port 280 # http-mgmt
acl Safe_ports port 488 # gss-http
acl Safe_ports port 591 # filemaker
acl Safe_ports port 777 # multiling http
acl Safe_ports port 631 # cups
acl Safe_ports port 873 # rsync
acl Safe_ports port 901 # SWAT
acl Safe_ports port 8443 # special web
acl purge method PURGE
acl CONNECT method CONNECT

http_access allow manager localhost
http_access deny manager
http_access allow purge localhost
http_access deny purge
http_access deny !Safe_ports
http_access deny CONNECT !SSL_ports
http_access allow localhost

acl company src 192.168.0.0/16
http_access allow company

http_access deny all

icp_access allow all
http_port 192.168.0.15:8080 accel defaultsite=fu.company.com
cache_peer 172.0.0.1 parent 8080 0 no-query originserver

hierarchy_stoplist cgi-bin ?

cache_dir ufs /var/spool/squid 1024 16 256

access_log /var/log/squid/access.log squid

acl QUERY urlpath_regex cgi-bin \?
cache deny QUERY

refresh_pattern ^ftp: 1440 20% 10080
refresh_pattern ^gopher: 1440 0% 1440
refresh_pattern . 0 20% 4320

acl apache rep_header Server ^Apache
broken_vary_encoding allow apache

extension_methods REPORT MERGE MKACTIVITY CHECKOUT

visible_hostname prod-iproxy.company.com

hosts_file /etc/hosts

coredump_dir /var/spool/squid

#############################################################
Thanks,
Jan

On Tue, Dec 9, 2008 at 5:02 PM, Dean Weimer <dweimer_at_orscheln.com> wrote:
> What version of squid are you running, and can you include the configuration lines that you used to configure the reverse proxy settings?
>
> Thanks,
> Dean Weimer
> Network Administrator
> Orscheln Management Co
>
> -----Original Message-----
> From: Jan Welker [mailto:jan.welker_at_gmail.com]
> Sent: Tuesday, December 09, 2008 9:40 AM
> To: squid-users_at_squid-cache.org
> Subject: Re: [squid-users] Netscape to Squid conversion Issues
>
> I do have a webserver hosting the pac file. I set the default site to
> be that webserver. I do not get it to work. I followed this manual:
> http://wiki.squid-cache.org/SquidFaq/ReverseProxy
>
>
> On Tue, Dec 9, 2008 at 4:26 PM, Dean Weimer <dweimer_at_orscheln.com> wrote:
>> You might try configuring squid as a reverse proxy for a web server actually hosting your proxy.pac file, I have never tried this, but I think it would work.
>>
>> Thanks,
>> Dean Weimer
>> Network Administrator
>> Orscheln Management Co
>>
>> -----Original Message-----
>> From: Jan Welker [mailto:jan.welker_at_gmail.com]
>> Sent: Tuesday, December 09, 2008 8:04 AM
>> To: squid-users_at_squid-cache.org
>> Subject: [squid-users] Netscape to Squid conversion Issues
>>
>> Here's a situation we're facing and I'm curious if anyone has some
>> insight into how we might approach this problem.
>>
>> We currently have approximately pcs, a very large portion of which
>> are configured in one of two ways.
>>
>> 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).
>>
>> This setup runs fine when pointing to the netscape admin-server/proxy
>> server configuration.
>>
>> The problem I'm having is when I point one of the "automatic"
>> configured pcs to one of the boxes running SQUID. At startup, the user
>> receives a message saying the automatic configuration has failed and
>> on the squid server I see the following access.log entry.
>>
>> 10.49.0.145 - - [30/Apr/2001:16:28:40 -0400] "GET / HTTP/0.0" 400 1094 NONE:NONE
>>
>> From the docs, it's clear that I need to provide a proxy.pac file
>> telling the users what their automatic configuration should be. The
>> problem I'm having is how to provide this info and provide
>> filtering/caching all from the same port?
>>
>> Having all the users change their configuration to point to another
>> port or host isn't an attractive option (120+ sites, 6000 pcs likely
>> 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.
>>
>> Any insight would be greatly appreciated.
>>
>> Jan
>>
>
Received on Tue Dec 09 2008 - 17:04:00 MST