RE: [squid-users] Squid and Windows Update.

From: Sturgis, Grant <Grant.Sturgis@dont-contact.us>
Date: Wed, 3 Dec 2003 16:47:44 -0700

I am having the exact problem (see my post from yesterday). I have created a temporary work around by adding:

acl windowsupdate dstdomain .windowsupdate.microsoft.com
no_cache deny windowsupdate

to squid.conf.

Any other ideas?

Grant

-----Original Message-----
From: Mike McCall [mailto:mccall@rrdo.rrps.k12.nm.us]
Sent: Wednesday, December 03, 2003 7:38 AM
To: squid-users@squid-cache.org
Cc: 'Palmer J.D.F.'
Subject: RE: [squid-users] Squid and Windows Update.

I'm having the same issue here too, which I first noticed yesterday. It
looks like https://v4.windowsupdate.microsoft.com/ works though. I assume
that because Squid just relays SSL traffic, whatever causes the non-secure
site to break is not affected.

Any ideas on a permanent fix or workaround would be appreciated, though!

Mike

-----Original Message-----
From: Palmer J.D.F. [mailto:J.D.F.Palmer@Swansea.ac.uk]
Sent: Wednesday, December 03, 2003 7:19 AM
To: squid-users@squid-cache.org
Subject: [squid-users] Squid and Windows Update.

Hello,

I'm having a bit of an issue with Squid and Windows Update.
In the last day or so we have noticed machines on campus failing to get
their WUs.

All goes well until I click the "scan for updates" link and then I get an
error, the M$ error is the seemingly infamous '0x800a138F' error.

Many pages from the search below blame the new hosting arrangements that M$
have with Akamai, stating that Akamai are also a host for many ad banners so
are often blocked by admin's.
http://www.google.com/search?sourceid=navclient&ie=UTF-8&oe=UTF-8&q=0x800a13
8F

However we don't appear to have any rules in our squid.conf that block
access to that site, neither when I log the requests from my test machine
does it deny access to any of the requests; Anyway on further investigation
I have retrieved another M$ error code from the WU Log file on the client
PC, this is '0x800C0002' which according to M$ is "Invalid URL".

I only get this problem going through the squid boxes.

Another twist to this is that if I turn the cache settings off in IE do a WU
scan which succeeds and then turn the cache settings back on it works fine
thereafter. However it is not possible for us to turn the cache setting off
all the machines here, even if it were we'd have to open up the firewall to
allow port 80 access for all machines rather than just the WWW and a select
few admin machines.

Is this a known bug with squid?

Many thanks,
Jezz Palmer.

****************************************
Jezz Palmer.
Internet Systems Officer.
Library and Information Services
University of Wales, Swansea
Singleton Park
Swansea
SA2 8PP
****************************************

This electronic message transmission is a PRIVATE communication which contains
information which may be confidential or privileged. The information is intended
to be for the use of the individual or entity named above. If you are not the
intended recipient, please be aware that any disclosure, copying, distribution
or use of the contents of this information is prohibited. Please notify the
sender of the delivery error by replying to this message, or notify us by
telephone (877-633-2436, ext. 0), and then delete it from your system.
Received on Wed Dec 03 2003 - 16:47:20 MST

This archive was generated by hypermail pre-2.1.9 : Thu Jan 01 2004 - 12:00:05 MST