From: Ed Summers <ehs@po...> - 2003-10-30 23:01:55
On Thu, Oct 30, 2003 at 05:35:30PM -0500, Lewis, Erik wrote:
> All your talking about is a list of blocked sites. The nuts and bolts are
> already in Squid. Which is what commercial vendors have already
> discovered. DansGuardian is pretty nice had several of my libraries using
> it before we went to a Cisco solution. Which is Squid repackaged.
Having a list of blocked sites is pretty rudimentary. I was under the
impression that most services would block based on analysis of the content? I
must admit, I have no direct experience with HTTP content filters.
> Thanks for the tidbit on large POST issues. Thats a good keeper in terms of
> things to remember when running squid and squid based solutions. I'd be
> curious how did you discover it? Was it serendipity or are there any
> telling signs.
The telling sign was our customers calling and saying,
I hit the submit button, and I get "This Page Cannot Be Displayed"
in IE. What gives?
Then we looked in the server logs, and sure enough we never even
received the POST, and deduced it had been intercepted by a proxy. Some
helpful filtering vendors helped us confirm that the proxy settings
were such that the large POST was being turned back.