On 30/06/2015 7:45 p.m., Stakres wrote: > Hi Antony, > > Correct, the kid contacts the parent that is getting a 504 and replies the > same to the kid. That's why I suspect the parent tries to download by itself > instead replying to the kid it does not have the object so the kid should do > a fresh download from internet. Lets get this clear. There is *no* kid and *no* parent involved in this transaction. There is a client sibling, and a server sibling. The client sibling uses CacheDigest to identify that the server sibling probably has the object in cache so it fetches from the server sibling. The server sibling responds with 504. If it is possibel to re-forward the request to another destination the client sibling *will* retry one of those after a 504. Enable "debug_options 17,5" to see the re-forwarding operations in action. Unfortunately not all reasons for non-retry are logged, but it gives a good idea of whats going on anyway. Amos _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
