Sounds good. If I have 5 multicast siblings (squid) then DR origin set as sibling but originserver flag, then Primary web servers as parent will it still follow the heirachy? So squid multicast siblings, then if object not found DR sibling/origin servers, and then primary parent before it gives a 404 if it is not found on the parent? That would be awesome if that works :-) will test once I get to the office. Chris Toft Mob: 0459 029 454 On 22/11/2010, at 19:30, "Amos Jeffries" <squid3@xxxxxxxxxxxxx> wrote: > On 22/11/10 18:56, Chris Toft wrote: >> Hi, >> >> Can squid detect a 404 from the origin servers? >> >> OK scenario is such: 2 data centres with backend storage. The DR >> datacentre is between 3 and 5 mins lag on the storage being mirrored >> but want to run active active data centres. >> >> So if someone hits the DR datacentre after an image that was uploaded >> to primary say 2 mins after the upload when it goes to the DR >> datacentre origin servers they will send a 404 as the image hasn't >> yet sync'd across. >> >> When this happens is it possible to configure squid that if it gets a >> 404 from origin at DR it will then check the origin servers in the >> primary site for the object? > > What you want seems to match with the case of configuring DR server as a > *sibling* type with originserver flags. These are tested before parent > types. > > Amos > -- > Please be using > Current Stable Squid 2.7.STABLE9 or 3.1.9 > Beta testers wanted for 3.2.0.3 The information contained in this e-mail message and any accompanying files is or may be confidential. If you are not the intended recipient, any use, dissemination, reliance, forwarding, printing or copying of this e-mail or any attached files is unauthorised. This e-mail is subject to copyright. No part of it should be reproduced, adapted or communicated without the written consent of the copyright owner. If you have received this e-mail in error please advise the sender immediately by return e-mail or telephone and delete all copies. Fairfax does not guarantee the accuracy or completeness of any information contained in this e-mail or attached files. Internet communications are not secure, therefore Fairfax does not accept legal responsibility for the contents of this message or attached files.
