Henry C. wrote: >> > /sidebar: it would be great if ats had a config option to "normalise" > these > headers so that an object is seen as cached by all clients. That would > probably break something or other, I suppose. However, for our case, it's
It *does* indeed have an option to normalize the by far most common header used for Vary, which is accept-encoding. For this, it has an option to identify "gzip" vs non-gzip, and therefore can deal with the fact that there are literally thousands of ways browsers express that they support gzip. For the generic case, it's very, very difficult to do something similar. All i can suggest is to write a plugin for it. Or, wait for us to get the Lua plugin interface in order (yeah, I know, I suck ...), then it'd be even easier to just tweak the User-Agent: header accordingly. Or, don't Vary: on somethng that has so much entropy :). Even if you fix this on ATS (or varnish or squid), all upstream intermediaries will have the same problem, and will have a difficult time caching the content efficiently. Cheers, -- Leif
