I have what I believe is a unique need. Here's the skinny:

We've been using BM for several years. In the past year or two, technology
has changed quite a bit, and we are seeing many file sharing programs using
port 80. Our student population seems to be using this quite a bit these
days. The result is that we are seeing as much or more data being streamed
_outbound_ through BM as inbound, and a very low caching rate (15%), even
when configured according to CJ's recommendations (thanks again, Craig).

This has caused the server to become relatively unstable. By that, I mean
that, compared to our other BM server that is used only by staff. It either
self-reboots or lockes up (no keyboard control but screen still updates)
every few days.

I was wondering if it's time to abandon proxy as such and, instead, set it
up as just a filtering server with no caching being performed. An ideal
scenario would be one where it worked more like a router than a proxy, not
making HTTP requests on behalf of the user but just forwarding the request
on, while still performing filtering on the URL's (we use BESS).

We need to continue to offer filtering, and need to keep the SSO
capabilities of CLNTRUST. But we don't need it to cache or serve as a
proxy. Could/should this be done with BM?

(Please assume that turning off caching would not have a appreciable
negative impact on our bandwidth for this disucssion.)


Curtis Spears
Sr. Network Administrator
Northwest Nazarene University