Re: squid cache
On Sun, Oct 14, 2001 at 07:58:30PM +0200, Carsten Leonhardt wrote:
> Brian May <bam@debian.org> writes:
>
> > Over 2 hours later, the first computer downloads it *again* for some
> > unknown reason which I really can't remember:
> >
> > 1002876131.609 403940 192.168.87.132 TCP_MISS/206 4194 GET http://ftp.au.debian.org/pub/debian/pool/main/a/apt/apt_0.5.4_i386.deb - DIRECT/203.16.234.19 application/x-debian-package
> >
> > and again:
> >
> > 1002876199.324 67714 192.168.87.132 TCP_MISS/206 247895 GET http://ftp.au.debian.org/pub/debian/pool/main/a/apt/apt_0.5.4_i386.deb - DIRECT/203.16.234.20 application/x-debian-package
>
> Maybe you'll have more luck if you use a specific IP address. The
> first request is to 203.16.234.19, the second to .20
This is just round-robin DNS for ftp.au.debian.org, and won't affect
caching at all. Squid's object identity is based on the URL itself, not
where it retrieved it from (parent/sibling cache, direct, one IP or
another).
--
- mdz
Reply to: