Yep that's right. The filter is too stupid to beable to pick up the
q=cache if it is elsewhere in the url instead of just after 'search?'.

It could be done with a regexp list but we've never bothered. Filtering
stuff like that out is stupid. A determined person is always going to
get around the problem. And frankly, they deserve to! :-)

The Internet considers censorship to be damage and routes around it.

-John Gilmore.


On Wed, 27 Mar 2002, John J. Yatsko, Jr. wrote:

> Here's an interesting peice on Google cache blocking and Bess... how to do
> it, some "other" holes, etc.
>
> http://www.sethf.com/anticensorware/bess/google.php
>
>
> John Yatsko, Jr.
> Technology Assistant
> Erie County Public Library
> 160 East Front St
> Erie PA 16507
> (814) 451-7307
>
> ----- Original Message -----
> From: "Chris Fletcher" <[EMAIL PROTECTED]>
> To: "Falconer, Craig" <[EMAIL PROTECTED]>
> Cc: "SquidGuard Mailing List" <[EMAIL PROTECTED]>
> Sent: Wednesday, March 27, 2002 2:00 AM
> Subject: Re: Google cache blocking
>
>
> > Had the same problem. We fixed it with a url block of:
> > google.com/search?q=cache
> >
> > >From then on any google cache sites where blocked.
> >
> > On Wed, 27 Mar 2002, Falconer, Craig wrote:
> >
> > > Google - you're a god - but WHY do you have a publicly-readable cache???
> > >
> > > I'm seeing a lot of students using the google cache to bypass blocks.
> What
> > > can I do?
> > >
> > > They don't get any graphics on their page though.  Any suggestions
> (short of
> > > blocking google completely (isn't that akin to heresy?))
> > >
> > >
> > >
> > >
> > >
> >
>
>

Reply via email to