RE: [squid-users] Windows Updates on 3.2.6

From: Dave Burkholder <dave_at_thinkwelldesigns.com>
Date: Thu, 31 Jan 2013 09:54:46 -0500

Are there any comments here? I've tried adding the following options from http://wiki.squid-cache.org/SquidFaq/WindowsUpdate (even though I don't especially want to cache updates)

range_offset_limit -1
maximum_object_size 200 MB
quick_abort_min -1

No joy. I've tried transparent & standard proxy modes. Not using authentication anywhere. I've now tested on 4 LANs behind Squid 3.2.6 on CentOS 5 & 6 machines and WU isn't working on any of them.

On one machine I downgraded to 3.2.0.18 and was able to get WU to work. Was there a regression since 3.2.0.18?

Thanks,

Dave

-----Original Message-----
From: Dave Burkholder
Sent: Wednesday, January 30, 2013 9:09 PM
To: squid-users_at_squid-cache.org
Subject: [squid-users] Windows Updates on 3.2.6

Hello everyone,

I've upgraded a number of machines from 3.1.12 to squid 3.2.6. Since then, Windows Updates haven't completed and I'm totally scratching my head.

Has anyone else experienced this problem? (I'm including my config file below.) Or have some ACLs or defaults changed in 3.2.x that might be triggering this?

Thanks,

Dave

 

#
# Recommended minimum configuration:
#
# webconfig: acl_start
acl webconfig_lan src 192.168.0.0/16 10.0.0.0/8 acl webconfig_to_lan dst 192.168.0.0/16 10.0.0.0/8 # webconfig: acl_end

# Example rule allowing access from your local networks.
# Adapt to list your (internal) IP networks from where browsing # should be allowed

acl SSL_ports port 443
acl SSL_ports port 81 83 10000 # Webconfig / Webmail / Webmin
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 81 83 10000 # Webconfig / Webmail / Webmin
acl CONNECT method CONNECT

#
# Recommended minimum Access Permission configuration:
#
# Only allow cachemgr access from localhost http_access allow manager localhost http_access deny manager http_access allow webconfig_to_lan

# Deny requests to certain unsafe ports
http_access deny !Safe_ports

# Deny CONNECT to other than secure SSL ports http_access deny CONNECT !SSL_ports

# We strongly recommend the following be uncommented to protect innocent # web applications running on the proxy server who think the only # one who can access services on "localhost" is a local user #http_access deny to_localhost

#
# INSERT YOUR OWN RULE(S) HERE TO ALLOW ACCESS FROM YOUR CLIENTS

# Example rule allowing access from your local networks.
# from where browsing should be allowed
http_access allow localhost

# And finally deny all other access to this proxy http_access allow webconfig_lan http_access deny all

# Squid normally listens to port 3128
http_port 3128

# We recommend you to use at least the following line.
hierarchy_stoplist cgi-bin ?

# Uncomment and adjust the following to add a disk cache directory.
cache_dir ufs /var/spool/squid 2048 16 256

# Leave coredumps in the first cache dir coredump_dir /var/spool/squid

follow_x_forwarded_for allow localhost

# Add any of your own refresh_pattern entries above these.
refresh_pattern ^ftp: 1440 20% 10080
refresh_pattern ^gopher: 1440 0% 1440
refresh_pattern -i (/cgi-bin/|\?) 0 0% 0
refresh_pattern . 0 20% 4320
redirect_program /usr/sbin/adzapper
maximum_object_size 51200 KB
Received on Thu Jan 31 2013 - 14:55:07 MST

This archive was generated by hypermail 2.2.0 : Thu Jan 31 2013 - 12:00:04 MST