you may configure the two squids as siblings behind the loadbalancer to eliminate the need to pre-cache on both squids. On Wed, Oct 27, 2010 at 9:42 AM, Sokol, Ryan - 1244 <ryans@xxxxxx> wrote: > -----Original Message----- > From: Amos Jeffries [mailto:squid3@xxxxxxxxxxxxx] > Sent: Tuesday, October 26, 2010 7:23 PM >> Definitely not. Relative URLs are not unique. Visit the "/" page from >> http://example.com/ and imagine what complaints you would get if it >> appeared instead of your own website "/" page. > > But I only have one site that I'm proxying, so the non-domain part of all URLs cached is exactly the same. http://www.domain.com/object.html is exactly the same as http://squid1.domain.com/object.html. > >> * There is no requirement for you to send the absolute URL >> "http://squid1.domain.com/object.html"; to your squid1. You can as easily >> contact it directly: >> squidclient -h squid1 http://www.example.com/object.html > > Great! Didn't know that tool exists. It is certainly one way to precache. > >> * Also, pre-caching has a very limited set of uses. Check that you >> actually need to do this before wasting bandwidth. > > My squids sit in front a dynamic imaging server that often takes 10-15 seconds to generate the resulting image. I don't want my customers to have to wait for these images, so I precache for them. > >
