Re: [squid-users] problem with site that is not supposed to be cached

Are you sure the site is just "not supposed to be cached". Perhaps it
is not supposed to be proxied?

Sounds kinda like an authentication scheme that cannot be proxied is
being used, and it sounds like you're expecting Squid not to proxy
requests when the no_cache directive is used. Squid can't not proxy a
request once it receives it--it can proxy it, or close the connection.
Whether it caches the request is orthogonal, and clearly not the source
of the problem here.

Add this site to your WCCP bypass list in your router, or you can bypass
it in the cache if WCCP redirection happens on a different leg than the
Squid box lives on.

Chad Whitten wrote:

> i am having a problem with a site that is not supposed to be cached.
> i have
> the following in squid.conf
>
> acl AIMCO url_regex ^http://intranet.aimco.com/$
> no_cache deny AIMCO
>
> running squid version Squid Cache: Version 2.4.STABLE7
> on linux - kernel 2.4.19 in transparent mode with wccp version 1 on a
> cisco
> router.
>
> everything works fine for everyone else, just this site is not
> supposed to be
> cached because its an intranet/vpn site. before i addd the no_cache
> directive, the user would just be prompted for password over and over.
> now
> they get past that but get 'page cannot be displayed message from ie'.
> squid
> still seems to be logging a lot of traffic from that site - mostly
> TCP_MISS/401 logs.
>
> any suggestions?
>

-- 
Joe Cooper <joe@swelltech.com>
Web caching appliances and support.
http://www.swelltech.com