Re: broken regex, refresh_pattern, or request_/reply_header?

the *_header_access directives can only change the external view of the
headers sent by Squid, not how Squid parses received headers.

To override "bad" things sent by client or server you need to use
refresh_pattern overrides. In your case both the ignore-reload and
ignore-private overrides.

Be warned that both these violate the HTTP specifications so you better
know what you are doing when using these.. if used carelessly you may
well end up sending one users private bank account details to another
user..

On fre, 2008-09-12 at 14:48 -0500, Ritter, Nicholas wrote:
> I might be way off on this, but I am wondering if it is my config, or if
> it is the squid code. I am using squid-3.HEAD-20080910 and I an trying
> to block Cache-Control headers in addition to control the fresh pattern
> of jar files, but nothing seems to work.
>
> I tried various regex patterns including:
>
> urlpath_regex -i \.jar$
>
> and even (just to see if it was my regex or something else):
>
> request_header_access Cache-Control deny all
> reply_header_access Cache-Control deny all
>
>
> as well as (just to see if it was my regex or something else):
>
> refresh_pattern -i \.jar$ 480 20% 1440 ignore-no-cache
> ignore-no-store override-expire override-lastmod
> refresh_pattern . 0 20% 4320 ignore-no-cache
> ignore-no-store override-expire override-lastmod
>
> Despite even the drastic attempts, the access.log still sees
> "TCP_CLIENT_REFRESH_MISS/200"
>
> A sniffer shows that the client is emmitting "Cache-Control: no-cache"
> and "Pragma: no-cache" headers fir the request, and the server is
> emitting a "Cache-Control: private" header.
>
> Nick
Received on Fri Sep 12 2008 - 20:08:03 MDT