Re: apt with index diff support
Florian Weimer <email@example.com> writes:
> * Michael Vogt:
>> When fully supported by the archive, the diff support will be
>> completely transparent, no changes on your side necessary.
> When downloading the Index file, APT does not send instructions to
> bypass the proxy cache:
> T 220.127.116.11:51459 -> 18.104.22.168:9999 [AP]
> GET /debian/dists/experimental/main/source/Sources.diff/Index HTTP/1.1..Hos
> t: proxy.enyo.de:9999..Connection: keep-alive..User-Agent: Debian APT-HTTP/
> 1.3....GET /debian/dists/unstable/main/binary-i386/Packages.bz2 HTTP/1.1..H
> ost: proxy.enyo.de:9999..Connection: keep-alive..Range: bytes=246835-..If-R
> ange: Fri, 28 Oct 2005 19:18:20 GMT..User-Agent: Debian APT-HTTP/1.3....
> (This is with apt 0.6.42.1exp1.)
> This means that apt-proxy (and probably other proxies as well) returns
> a stale copy. Sure, this could be fixed on the proxy side, but I
> think to actually achieve the transparency you are aiming at, you have
> to implement a workaround in APT.
Doesn't the 'If-Range: Fri, 28 Oct 2005 19:18:20 GMT' mean the proxy
should query upstream? Also what is the time to live on the reply? And
shouldn't the proxy always query for an update if the TTL is gone?
I don't want to download the diff every time. Not when I update a
32 Nodes cluster over one proxy within minutes. So just plainly
baypassing the proxy seems wrong.
> (Apart from that, I can only repeated what I already wrote a couple of
> weeks ago: Nice work.)
PS: Is the index file listed in Release?