RE: [squid-users] Pessimal behavior with Windows Update (Long)

> -----Original Message-----
> From: Brett Glass [mailto:squid-users@brettglass.com]
> Sent: Wednesday, June 29, 2005 8:12 AM
> To: Chris Robertson; 'Brett Glass'
> Cc: Squid-users@squid-cache.org
> Subject: RE: [squid-users] Pessimal behavior with Windows Update (Long)
>
>
> At 04:08 PM 6/28/2005, Chris Robertson wrote:
>
>>5. Set up a separate "big file" proxy (could just be a second squid
instance
>>on the same box) that caches large requests. Set the main proxy server to
>>only cache files of a "sane" size. Use the "big file" proxy as a parent
for
>>said domains (never_direct and always_direct would manage this). Not
>>optimal, perhaps not even pretty, but it will save you from caching 400MB
of
>>streaming music.
>
> Why go to all this trouble (and expend all of those resources) when all it

> takes to fix the problem is to add ACL capability to one Squid parameter?
>
> --Brett Glass

Why go through the trouble? Two reasons...

1) Because I am a Squid admin, not a C programmer. One path is feasible for
me (using the program provided), one is not (updating the source provided).
2) The squid 2.5 branch is feature locked. I have no idea how willing the
developers are going to be adding acl functionality.

*shrug*

I'm was not trying to make any less of your suggestions, and/or problems.
My intention was just to provide an alternate solution.

Chris
Received on Wed Jun 29 2005 - 13:20:33 MDT