Bug#28172: HTTP Proxy cache refresh should be forced for corrupt packages
In article <[🔎] 199810190459.VAA23936@yelm.east.bacchus.com> you write:
>Package: apt
>Version: 0.1.7
>
>If apt uses a proxy and detects that a package is corrupt (for
>example, detecting a MD5 checksum mismatch or an appropriate error
>while unpacking), then steps need to be taken to ensure that bad data
>in any intermediate caches is flushed. Otherwise, apt often winds up
>getting the same corrupt package over and over.
>
>A possible strategy is to track which packages are corrupt and, on
>the next download, include a 'Cache-Control: no-cache' header for
>HTTP/1.1 proxies and/or a 'Pragma: no-cache' for HTTP/1.0 proxies
>to force intermediate caches to obtain a new copy ('Cache-Control:
>max-age=0' is not sufficient).
>
>Eventually, if the proposed HTCP protocol is widely deployed by
>proxies, it might be possible to use that mechanism to ask the proxies
>to delete their copies of corrupt packages.
Maybe this is irrelevant in the latest version of apt (I can't remember
off hand what version I have), but I get messages that a package is
currupt, when in fact the only problem was that APT timed out during
the transfer.
If you are going to force flushing of the cache, make sure it isn't
just because of a time out error, where flushing the cache might
considerably slow things down.
[ sidenote: I often --> always get time out errors
transferring files onto my computer, but this is not relevant to
APT. I think it is a combination of using the development kernels
and/or slow ISP. ]
Reply to: