Search squid archive

Re: Re: Create acl based on Accept-Language?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 26/08/2013 10:03 p.m., Manuel wrote:
OK so we can only have one cached copy per URL, is that correct?

No variant caching is supported by Squid. The server just has to send the Vary:Accept-Language. Adding them by Squid or ICAP seems not to be enough, but will help downstream clients cache it properly.


  If so the
only solution I can think of is by at least using that copy for the main
content and once an user requests the Italian version of the content we can
always provide the user with non-cached content and non-caching the content,
correct?

To do so what we have to do is to just add:
cache deny itlanguage

right?

If you wish.

What in any case surprises me is that in the example I gave you requests
affected by acl specialuser is always fetching the content from the
cache_peer named specialserver despite there is almost always a cached copy
of the exact URL that requests (which is the base URL http://www.xxxxxx.com/
)

With regards to the HTTP responses the reverse proxy is ignoring them
(override-expire ignore-reload ignore-no-cache) and Squid decides what to
cache, what not to cache, etc. by the rules based on acl,
refresh_pattern....

Amos




[Index of Archives]     [Linux Audio Users]     [Samba]     [Big List of Linux Books]     [Linux USB]     [Yosemite News]

  Powered by Linux