Re: Idea for structure of Apt-Get
firstname.lastname@example.org (Lennart Sorensen) writes:
> On Fri, Apr 01, 2005 at 09:55:01PM +0200, Goswin von Brederlow wrote:
>> The ISps with caching proxies are usualy the ones that always have
>> problems with apt-get and basicaly any other http/ftp app, esspecialy
>> ftp. They start to cache stuff they aren't supposed to cache or don't
>> notice file changes.
>> Just think what happens if you get todays Release file and yesterdays
>> Packages file. Apt currnetly just fails to find packages but with 0.6
>> it will detect network intrusion and loudly scream as checksums don't
> Transparent proxies that don't do a good job rechecking documents are
> broken. If apt knows it is using a proxy it can request a check for
> updates on importante files (and does so). It works great. Nothing
> wrong with apt or proxies, only with transparent proxies that aren't
> that transparent.
> Len Sorensen
How do you tell apt that it is using a transparent proxy? How do you
tell an ftp proxy to ignore proxied files?
The problem with ISPs with transparent proxies is that many of them
are broken. Broken to a point that you can't fix it.
Even squid as ftp proxy is broken and doesn't notice file changes. How
do you expect some proprietary proxy to be better?