You are totally right ! The problem was on my side with the acl regular expression used to choose extensions to be cached: acl images url_regex -i \.(bmp|gif|ico|jpeg|jpg|png|svg|tif|tiff|webp)$ $ was not matching for '?query-string'
* Your answer helps me to find my error. * And I am now thinking about changing the way of doing the cache (a special refresh for my acls or/and a default to 0 0% 0 to use the TCP_REFRESH_UNMODIFIED). Thank you very much :) And sorry for the sound ! :( On Tue, Jul 13, 2021 at 8:23 PM <squ...@treenet.co.nz> wrote: > On 2021-07-13 05:59, Vincent Tamet wrote: > > Hi, > > > > I would like to know how to deactivate the "?" refresh_pattern filter > > ? > > There is no such filter. So "deactivate" has no meaning. > > refresh_pattern is a directive that provides default values for the > caching Freshness heuristics defined by RFC 7234. For messages without a > necessary cache-control or related header value. > > > > (As most web pages nowaday should use cache-control or expire, I guess > > the correct usage of headers should be enough to permit us to cache > > requests with "?" !? > > Yes. URLs containing '?query-string' are cached by Squid with the > default squid.conf refresh_pattern settings. > > The refresh_pattern line you noticed is to cope with servers that are > very old and/or broken. You can remove it, but any of your clients > visiting such a server will see the brokenness and probably blame Squid > because "it works fine with just Browser X". > > > Amos > _______________________________________________ > squid-users mailing list > squid-users@lists.squid-cache.org > http://lists.squid-cache.org/listinfo/squid-users
_______________________________________________ squid-users mailing list squid-users@lists.squid-cache.org http://lists.squid-cache.org/listinfo/squid-users
