[squid-users] Re: RE [squid-users] Update Accelerator, Squid and Windows Update Caching
I am also interested in this topic. I have several offices running Windows XP but have a Suse Linux server sitting in all the offices as a caching device. It would be nice to have the clients in all the offices get their updates from the server in their office instead of coming back to the corporate office to get them from the WSUS box. Anyone figure this out? Tim Bates wrote: Ricardo Augusto de Souza wrote: Why the hell do u want to cache windowsupdate? Just install a WSUS ( http://technet.microsoft.com/en-us/wsus/default.aspx ) in one windows machine in your LAN and it will download windowsupdate and send it to your local machines. Perhaps because clients can't be controlled... EG: People accessing the net via a public WiFi network, or boxes behind an ISP transparent proxy. Not every use of Squid is in a corporate LAN. I'm interested in a solution to caching Windows Updates because I work for a computer shop and we do updates on customer's PCs every day. We can't go telling those PCs to use a WSUS box because they leave the LAN 10 minutes later. TB -- View this message in context: http://www.nabble.com/RE--squid-users--Update-Accelerator%2C-Squid-and-Windows-Update-Caching-tp19919421p20388284.html Sent from the Squid - Users mailing list archive at Nabble.com.
Re: [squid-users] Update Accelerator, Squid and Windows Update Caching
Amos Jeffries wrote:
Richard Wall wrote:
On Fri, Oct 10, 2008 at 12:30 PM, Amos Jeffries
[EMAIL PROTECTED] wrote:
Richard Wall wrote:
Hi,
I've been reading through the archive looking for information about
squid 2.6 and windows update caching. The FAQ mentions problems with
range offsets but it's not really clear which versions of Squid this
applies to.
All versions. The FAQ was the result of my experiments mid last
year. With
some tweaks made early his year since Vista came out.
We haven't done a intensive experiments with Vista yet.
Hi Amos,
I'm still investigating Windows Update caching (with 2.6.STABLE17/18)
First of all, I have been doing some tests to try and find out the
problem with Squid and Content-Range requests.
* I watch the squid logs as a vista box does its automatic updates
and I can see that *some* of its requests use ranges. (so far I have
only seen these when it requests .psf files...some of which seem to be
very large files...so the range request makes sense) See:
http://groups.google.hr/group/microsoft.public.windowsupdate/browse_thread/thread/af5db07dc2db9713
# zcat squid.log.192.168.1.119.2008-10-16.gz | grep
multipart/byteranges | awk '{print $7}' | uniq | while read URL; do
echo $URL; wget --spider $URL 21 | grep Length; done
http://www.download.windowsupdate.com/msdownload/update/software/secu/2008/10/windows6.0-kb956390-x86_2d03c4b14b5bad88510380c14acd2bffc26436a7.psf
Length: 91,225,471 (87M) [application/octet-stream]
http://www.download.windowsupdate.com/msdownload/update/software/secu/2008/05/windows6.0-kb950762-x86_0cc2989b92bc968e143e1eeae8817f08907fd715.psf
Length: 834,868 (815K) [application/octet-stream]
http://www.download.windowsupdate.com/msdownload/update/software/secu/2008/03/windows6.0-kb948590-x86_ed27763e42ee2e20e676d9f6aa13f18b84d7bc96.psf
Length: 755,232 (738K) [application/octet-stream]
http://www.download.windowsupdate.com/msdownload/update/software/crup/2008/09/windows6.0-kb955302-x86_1e40fd3ae8f95723dbd76f837ba096adb25f3829.psf
Length: 7,003,447 (6.7M) [application/octet-stream]
...
* I have found that curl can make range requests so I've been using
it to test how Squid behavesand it seems to do the right thing. eg
- First ask for a range : The correct range is returned X-Cache: MISS
- Repeat the range request : The correct range is returned X-Cache:
MISS
- Request the entire file: The entire file is correctly returned
X-Cache: MISS
- Repeat the request: X-Cache: HIT
- Repeat the previous range request: X-Cache: HIT
- Request a different range: X-Cache: HIT
curl --range 1000-1002 --header Pragma: -v -x http://127.0.0.1:3128
http://www.download.windowsupdate.com/msdownload/update/software/secu/2008/05/windows6.0-kb950762-x86_0cc2989b92bc968e143e1eeae8817f08907fd715.psf
/dev/null
Looking back through the archive I find this conversation from 2005:
http://www.squid-cache.org/mail-archive/squid-users/200504/0669.html
...but the behaviour there sounds like a result of setting:
range_offset_limit -1
Seems to me that Squid should do a good job of Windows Update caching.
There is another thread discussing how to override MS update cache
control headers:
http://www.squid-cache.org/mail-archive/squid-users/200508/0596.html
but I don't see anything evil in the server response headers
today. I guess the client may be sending no-cache headers...I'll
double check that later.
Is there some other case that I'm missing?
As I said. I have not seen Vista in detail. I just had to turn off my
old hack to get around the SP1 hanging. (that huge .psf perhapse?)
Never had to do anything with headers.
When I did my testing it was with outdated Win98-WinXP machines (often
needing SP1 in XP's case).
The WU on them made an HTTPS request (seems to be auth-related even
today) requested one or more update indexes fine. Then proceeded to
random-access range requests out of the middle of the update *.cabs
using dynamic urls at various update sites.
This was causing bandwidth blowout with all the MISS'es when I had
several machines a week coming through.
I _think_ but have no confirmation, that the early patch-tuesday
releases were done as large single .CAB files and a particular machine
may only need updating from individual fixes inside them.
As your test showed, fetching the whole file squid can handle the
ranges fine. It's when they are still in MISS state that ranges become
trouble.
I'm going to experiment, but if anyone has any positive or
negative experience of Squid and windows update caching, I'd be really
interested to hear from you.
In case Squid cannot do windows update caching by its self, I'm also
looking at integrating Update Accelerator
(http://update-accelerator.advproxy.net/) script with standard squid
2.6 and wondered if anyone else had any experience of this.
The update accelerator script is just a perl wrapper around wget which
is configured as a Squid url_rewrite_program. It's not clear
Re: [squid-users] Update Accelerator, Squid and Windows Update Caching
On fre, 2008-10-17 at 06:06 +0100, Richard Wall wrote: but I don't see anything evil in the server response headers today. I guess the client may be sending no-cache headers...I'll double check that later. Is there some other case that I'm missing? I think the missing partial object cache is the main culpit for windows update caching today. Another minor culpit is that sometimes SSL is used. But I think this is only some metadata requests. Regards Henrik signature.asc Description: This is a digitally signed message part
Re: [squid-users] Update Accelerator, Squid and Windows Update Caching
Richard Wall wrote:
On Fri, Oct 10, 2008 at 12:30 PM, Amos Jeffries [EMAIL PROTECTED] wrote:
Richard Wall wrote:
Hi,
I've been reading through the archive looking for information about
squid 2.6 and windows update caching. The FAQ mentions problems with
range offsets but it's not really clear which versions of Squid this
applies to.
All versions. The FAQ was the result of my experiments mid last year. With
some tweaks made early his year since Vista came out.
We haven't done a intensive experiments with Vista yet.
Hi Amos,
I'm still investigating Windows Update caching (with 2.6.STABLE17/18)
First of all, I have been doing some tests to try and find out the
problem with Squid and Content-Range requests.
* I watch the squid logs as a vista box does its automatic updates
and I can see that *some* of its requests use ranges. (so far I have
only seen these when it requests .psf files...some of which seem to be
very large files...so the range request makes sense) See:
http://groups.google.hr/group/microsoft.public.windowsupdate/browse_thread/thread/af5db07dc2db9713
# zcat squid.log.192.168.1.119.2008-10-16.gz | grep
multipart/byteranges | awk '{print $7}' | uniq | while read URL; do
echo $URL; wget --spider $URL 21 | grep Length; done
http://www.download.windowsupdate.com/msdownload/update/software/secu/2008/10/windows6.0-kb956390-x86_2d03c4b14b5bad88510380c14acd2bffc26436a7.psf
Length: 91,225,471 (87M) [application/octet-stream]
http://www.download.windowsupdate.com/msdownload/update/software/secu/2008/05/windows6.0-kb950762-x86_0cc2989b92bc968e143e1eeae8817f08907fd715.psf
Length: 834,868 (815K) [application/octet-stream]
http://www.download.windowsupdate.com/msdownload/update/software/secu/2008/03/windows6.0-kb948590-x86_ed27763e42ee2e20e676d9f6aa13f18b84d7bc96.psf
Length: 755,232 (738K) [application/octet-stream]
http://www.download.windowsupdate.com/msdownload/update/software/crup/2008/09/windows6.0-kb955302-x86_1e40fd3ae8f95723dbd76f837ba096adb25f3829.psf
Length: 7,003,447 (6.7M) [application/octet-stream]
...
* I have found that curl can make range requests so I've been using
it to test how Squid behavesand it seems to do the right thing. eg
- First ask for a range : The correct range is returned X-Cache: MISS
- Repeat the range request : The correct range is returned X-Cache: MISS
- Request the entire file: The entire file is correctly returned X-Cache: MISS
- Repeat the request: X-Cache: HIT
- Repeat the previous range request: X-Cache: HIT
- Request a different range: X-Cache: HIT
curl --range 1000-1002 --header Pragma: -v -x http://127.0.0.1:3128
http://www.download.windowsupdate.com/msdownload/update/software/secu/2008/05/windows6.0-kb950762-x86_0cc2989b92bc968e143e1eeae8817f08907fd715.psf
/dev/null
Looking back through the archive I find this conversation from 2005:
http://www.squid-cache.org/mail-archive/squid-users/200504/0669.html
...but the behaviour there sounds like a result of setting:
range_offset_limit -1
Seems to me that Squid should do a good job of Windows Update caching.
There is another thread discussing how to override MS update cache
control headers:
http://www.squid-cache.org/mail-archive/squid-users/200508/0596.html
but I don't see anything evil in the server response headers
today. I guess the client may be sending no-cache headers...I'll
double check that later.
Is there some other case that I'm missing?
As I said. I have not seen Vista in detail. I just had to turn off my
old hack to get around the SP1 hanging. (that huge .psf perhapse?)
Never had to do anything with headers.
When I did my testing it was with outdated Win98-WinXP machines (often
needing SP1 in XP's case).
The WU on them made an HTTPS request (seems to be auth-related even
today) requested one or more update indexes fine. Then proceeded to
random-access range requests out of the middle of the update *.cabs
using dynamic urls at various update sites.
This was causing bandwidth blowout with all the MISS'es when I had
several machines a week coming through.
I _think_ but have no confirmation, that the early patch-tuesday
releases were done as large single .CAB files and a particular machine
may only need updating from individual fixes inside them.
As your test showed, fetching the whole file squid can handle the ranges
fine. It's when they are still in MISS state that ranges become trouble.
I'm going to experiment, but if anyone has any positive or
negative experience of Squid and windows update caching, I'd be really
interested to hear from you.
In case Squid cannot do windows update caching by its self, I'm also
looking at integrating Update Accelerator
(http://update-accelerator.advproxy.net/) script with standard squid
2.6 and wondered if anyone else had any experience of this.
The update accelerator script is just a perl wrapper around wget which
is configured as a Squid url_rewrite_program. It's not clear to me
what this script is doing that Squid
Re: [squid-users] Update Accelerator, Squid and Windows Update Caching
On Fri, Oct 10, 2008 at 12:30 PM, Amos Jeffries [EMAIL PROTECTED] wrote:
Richard Wall wrote:
Hi,
I've been reading through the archive looking for information about
squid 2.6 and windows update caching. The FAQ mentions problems with
range offsets but it's not really clear which versions of Squid this
applies to.
All versions. The FAQ was the result of my experiments mid last year. With
some tweaks made early his year since Vista came out.
We haven't done a intensive experiments with Vista yet.
Hi Amos,
I'm still investigating Windows Update caching (with 2.6.STABLE17/18)
First of all, I have been doing some tests to try and find out the
problem with Squid and Content-Range requests.
* I watch the squid logs as a vista box does its automatic updates
and I can see that *some* of its requests use ranges. (so far I have
only seen these when it requests .psf files...some of which seem to be
very large files...so the range request makes sense) See:
http://groups.google.hr/group/microsoft.public.windowsupdate/browse_thread/thread/af5db07dc2db9713
# zcat squid.log.192.168.1.119.2008-10-16.gz | grep
multipart/byteranges | awk '{print $7}' | uniq | while read URL; do
echo $URL; wget --spider $URL 21 | grep Length; done
http://www.download.windowsupdate.com/msdownload/update/software/secu/2008/10/windows6.0-kb956390-x86_2d03c4b14b5bad88510380c14acd2bffc26436a7.psf
Length: 91,225,471 (87M) [application/octet-stream]
http://www.download.windowsupdate.com/msdownload/update/software/secu/2008/05/windows6.0-kb950762-x86_0cc2989b92bc968e143e1eeae8817f08907fd715.psf
Length: 834,868 (815K) [application/octet-stream]
http://www.download.windowsupdate.com/msdownload/update/software/secu/2008/03/windows6.0-kb948590-x86_ed27763e42ee2e20e676d9f6aa13f18b84d7bc96.psf
Length: 755,232 (738K) [application/octet-stream]
http://www.download.windowsupdate.com/msdownload/update/software/crup/2008/09/windows6.0-kb955302-x86_1e40fd3ae8f95723dbd76f837ba096adb25f3829.psf
Length: 7,003,447 (6.7M) [application/octet-stream]
...
* I have found that curl can make range requests so I've been using
it to test how Squid behavesand it seems to do the right thing. eg
- First ask for a range : The correct range is returned X-Cache: MISS
- Repeat the range request : The correct range is returned X-Cache: MISS
- Request the entire file: The entire file is correctly returned X-Cache: MISS
- Repeat the request: X-Cache: HIT
- Repeat the previous range request: X-Cache: HIT
- Request a different range: X-Cache: HIT
curl --range 1000-1002 --header Pragma: -v -x http://127.0.0.1:3128
http://www.download.windowsupdate.com/msdownload/update/software/secu/2008/05/windows6.0-kb950762-x86_0cc2989b92bc968e143e1eeae8817f08907fd715.psf
/dev/null
Looking back through the archive I find this conversation from 2005:
http://www.squid-cache.org/mail-archive/squid-users/200504/0669.html
...but the behaviour there sounds like a result of setting:
range_offset_limit -1
Seems to me that Squid should do a good job of Windows Update caching.
There is another thread discussing how to override MS update cache
control headers:
http://www.squid-cache.org/mail-archive/squid-users/200508/0596.html
but I don't see anything evil in the server response headers
today. I guess the client may be sending no-cache headers...I'll
double check that later.
Is there some other case that I'm missing?
I'm going to experiment, but if anyone has any positive or
negative experience of Squid and windows update caching, I'd be really
interested to hear from you.
In case Squid cannot do windows update caching by its self, I'm also
looking at integrating Update Accelerator
(http://update-accelerator.advproxy.net/) script with standard squid
2.6 and wondered if anyone else had any experience of this.
The update accelerator script is just a perl wrapper around wget which
is configured as a Squid url_rewrite_program. It's not clear to me
what this script is doing that Squid wouldn't do by its self.
Strange indeed.
I got update accelerator working with Squid but I'm still not
convinced that it's necessary (see above).
-RichardW.
Re: [squid-users] Update Accelerator, Squid and Windows Update Caching
Richard Wall wrote: Hi, I've been reading through the archive looking for information about squid 2.6 and windows update caching. The FAQ mentions problems with range offsets but it's not really clear which versions of Squid this applies to. All versions. The FAQ was the result of my experiments mid last year. With some tweaks made early his year since Vista came out. We haven't done a intensive experiments with Vista yet. I'm going to experiment, but if anyone has any positive or negative experience of Squid and windows update caching, I'd be really interested to hear from you. In case Squid cannot do windows update caching by its self, I'm also looking at integrating Update Accelerator (http://update-accelerator.advproxy.net/) script with standard squid 2.6 and wondered if anyone else had any experience of this. The update accelerator script is just a perl wrapper around wget which is configured as a Squid url_rewrite_program. It's not clear to me what this script is doing that Squid wouldn't do by its self. Strange indeed. Amos -- Please use Squid 2.7.STABLE4 or 3.0.STABLE9
[squid-users] Update Accelerator, Squid and Windows Update Caching
Hi, I've been reading through the archive looking for information about squid 2.6 and windows update caching. The FAQ mentions problems with range offsets but it's not really clear which versions of Squid this applies to. I'm going to experiment, but if anyone has any positive or negative experience of Squid and windows update caching, I'd be really interested to hear from you. In case Squid cannot do windows update caching by its self, I'm also looking at integrating Update Accelerator (http://update-accelerator.advproxy.net/) script with standard squid 2.6 and wondered if anyone else had any experience of this. The update accelerator script is just a perl wrapper around wget which is configured as a Squid url_rewrite_program. It's not clear to me what this script is doing that Squid wouldn't do by its self. Thanks. -RichardW.
Re: [squid-users] Update Accelerator, Squid and Windows Update Caching
On Fri, Oct 10, 2008 at 12:30 PM, Amos Jeffries [EMAIL PROTECTED] wrote: Richard Wall wrote: I've been reading through the archive looking for information about squid 2.6 and windows update caching. The FAQ mentions problems with range offsets but it's not really clear which versions of Squid this applies to. All versions. The FAQ was the result of my experiments mid last year. With some tweaks made early his year since Vista came out. We haven't done a intensive experiments with Vista yet. Thanks Amos, Okay. Well I'm planning on testing with Vista updates so I'll try and report my findings here. snip In case Squid cannot do windows update caching by its self, I'm also looking at integrating Update Accelerator (http://update-accelerator.advproxy.net/) script with standard squid 2.6 and wondered if anyone else had any experience of this. The update accelerator script is just a perl wrapper around wget which is configured as a Squid url_rewrite_program. It's not clear to me what this script is doing that Squid wouldn't do by its self. Strange indeed. I'll let you know how it goes :) -RichardW.
[squid-users] RE [squid-users] Update Accelerator, Squid and Windows Update Caching
Why the hell do u want to cache windowsupdate? Just install a WSUS ( http://technet.microsoft.com/en-us/wsus/default.aspx ) in one windows machine in your LAN and it will download windowsupdate and send it to your local machines. I hope you like my suggestion. -Mensagem original- De: Richard Wall [mailto:[EMAIL PROTECTED] Enviada em: sexta-feira, 10 de outubro de 2008 08:55 Para: Amos Jeffries Cc: squid-users@squid-cache.org Assunto: Re: [squid-users] Update Accelerator, Squid and Windows Update Caching On Fri, Oct 10, 2008 at 12:30 PM, Amos Jeffries [EMAIL PROTECTED] wrote: Richard Wall wrote: I've been reading through the archive looking for information about squid 2.6 and windows update caching. The FAQ mentions problems with range offsets but it's not really clear which versions of Squid this applies to. All versions. The FAQ was the result of my experiments mid last year. With some tweaks made early his year since Vista came out. We haven't done a intensive experiments with Vista yet. Thanks Amos, Okay. Well I'm planning on testing with Vista updates so I'll try and report my findings here. snip In case Squid cannot do windows update caching by its self, I'm also looking at integrating Update Accelerator (http://update-accelerator.advproxy.net/) script with standard squid 2.6 and wondered if anyone else had any experience of this. The update accelerator script is just a perl wrapper around wget which is configured as a Squid url_rewrite_program. It's not clear to me what this script is doing that Squid wouldn't do by its self. Strange indeed. I'll let you know how it goes :) -RichardW.
RES: [squid-users] Update Accelerator, Squid and Windows Update Caching
Good lucky on your research. Depending on what antivirus do u have, u can also make a server to virus definitions. I have around 400 clients, that's why I´d like WSUS and SAV with liveupdate. Let us know your findings. Cya. -Mensagem original- De: Richard Wall [mailto:[EMAIL PROTECTED] Enviada em: sexta-feira, 10 de outubro de 2008 11:18 Para: Ricardo Augusto de Souza Cc: [EMAIL PROTECTED] Assunto: Re: [squid-users] Update Accelerator, Squid and Windows Update Caching On Fri, Oct 10, 2008 at 3:10 PM, Ricardo Augusto de Souza [EMAIL PROTECTED] wrote: Why the hell do u want to cache windowsupdate? Just install a WSUS ( http://technet.microsoft.com/en-us/wsus/default.aspx ) in one windows machine in your LAN and it will download windowsupdate and send it to your local machines. I hope you like my suggestion. Hi Ricardo, I do like your suggestion :) but the trouble is that we don't have a suitable Windows server, only client workstations. * http://tinyurl.com/3pb6rt I'm inclined to agree that it would be a lot less hassle to just buy the appropriate version of windows and setup a WUS server, but on the other hand, it would be cool if caching of Windows updates (antivirus updates etc) was just transparently handled by Squid. I will continue my investigation and report back. -RichardW.
Re: [squid-users] Update Accelerator, Squid and Windows Update Caching
On lör, 2008-10-11 at 00:30 +1300, Amos Jeffries wrote: In case Squid cannot do windows update caching by its self, I'm also looking at integrating Update Accelerator (http://update-accelerator.advproxy.net/) script with standard squid 2.6 and wondered if anyone else had any experience of this. The update accelerator script is just a perl wrapper around wget which is configured as a Squid url_rewrite_program. It's not clear to me what this script is doing that Squid wouldn't do by its self. Strange indeed. Nothing strange. It's simply a persistent cache with no respect for HTTP cache rules. Impemented by using wget to mirror the files onto an Apache web server, combined with an url rewriter helper to make Squid fetch the objects from there instead of microsoft. Regards Henrik signature.asc Description: This is a digitally signed message part
Re: [squid-users] RE [squid-users] Update Accelerator, Squid and Windows Update Caching
Ricardo Augusto de Souza wrote: Why the hell do u want to cache windowsupdate? Just install a WSUS ( http://technet.microsoft.com/en-us/wsus/default.aspx ) in one windows machine in your LAN and it will download windowsupdate and send it to your local machines. Perhaps because clients can't be controlled... EG: People accessing the net via a public WiFi network, or boxes behind an ISP transparent proxy. Not every use of Squid is in a corporate LAN. I'm interested in a solution to caching Windows Updates because I work for a computer shop and we do updates on customer's PCs every day. We can't go telling those PCs to use a WSUS box because they leave the LAN 10 minutes later. TB
