On 4/11/2015 9:53 a.m., Yuri Voinov wrote: > > To talk was objective: show the config (squid.conf) and URL, which > causes problems with caching. Telepaths on holiday in Bali. Personally, > I have no idea either looks like configuration or a URL you're trying to > cache. In such a situation it is impossible to say anything definite. > It is an object apparently containing per-user information (Cache-Control:private). Note that Expires and max-age=N headers are meaningless on private objects. A private object needs revalidating on every single re-use. It is being served up from GoogleVideoServer (aka "gvs") so is either YouTube content (they go to some extreme lengths to prevent caches working), or possibly a video on someones personal account, or maybe with DRM embeded. The no-change on size could be an artifact of jo being the only one fetching it. Or the object may be padded by the server so its always a fixed size of crypted blocks to prevent DRM decryption attempts. jo is using "ignore-private" configuration option to make Squid cache the object. But that can only make it be stored. It cannot magically make the stored content useful. The revalidation which does make it useful still has to happen to ensure the right per-user headers are attached when it is delivered to the client. The server then barfs out a whole new copy in full when asked for revalidation details. Facing servers like this occasionally is part of the price we unfortunately pay for caching Cache-Control:private things without causing all sorts of far worse nasty side effects. jo; you could remove that "ignore-private" configuration option. That would not affect these particular objects bandwidth usage, but would free up the cache space they are currently using for caching other things with possibly better savings. Amos _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
