CrossNodes: Simple Configuration Tips Put Squid on the Menu (Parts 1 & 2)
Jun 28, 2004, 07:00 (0 Talkback[s])
(Other stories by Carla Schroder)
No-Size-Fits-All! An Application-Down Approach for Your Cloud Transformation REGISTER >
[ Thanks to Erinn
for these links. ]
From Part 1:
"If you've been running a network for any length of time, you
know that merely connecting to the Internet, then sitting back and
having fun, is simply not in the cards for us hardworking
netadmins. No, for all those bits must not be allowed to flow
unimpeded, but must be monitored, filtered, diverted, accepted,
rejected, sniffed, throttled, chained, and logged. It's a wonder
that any of them survive.
"The Squid http proxy performs a large number of useful tasks.
Today we'll look at http proxying and access controls. Squid's
primary duty is to cache http requests. A typical LAN has much
fatter internal pipes than external, so the bottleneck is usually
your shared Internet connection. Caching Web pages speeds things up
considerably, and conserves bandwidth. And you, the godlike admin,
can restrict access to specific Web sites, networks, and users, as
the whim... I mean necessity... dictates..."
Story (Part 1)
Story (Part 2)