Hallo,
* Steven Chamberlain [Sun, Aug 05 2012, 06:06:29PM]:
> found 683803 apt-cacher-ng/0.7.6-1
> thanks
>
> Hi,
>
> I was also testing apt-cacher-ng 0.7.6-1 today with http.debian.net
>
> I would have expected with default settings (ForceManaged 0, RedirMax 5)
> that apt-cacher-ng would follow the 302 redirects served by
> http.debian.net, retrieve the object from that other location, write it
> into its cache and serve the object directly to the client. Instead, it
That's the plan.
> seems to hang for some time, then pass the 302 redirect through to the
> client without writing the real object into cache.
After a quick analysis, I assume that the responsible behaviour might
only happen when the "special resuming code" gets active (a dirty little
helper: when the remote host suddenly disconects, it attempts to
reconnect in background and return the data starting from the last known
location). And that part has a known problem, it does not work with
302-redirection yet or if the mirror does not support resuming.
So, IMHO the root cause is http.debian.net redirecting you to a faulty
mirror. If you wish to know it's location, check the freshly created
*.head files in your cache (ideally the one belonging to the aborted
download).
> Also with RedirMax 0, the 302 redirect is forwarded immediately through
> to the client, so nothing is cached, making apt-cacher-ng pointless in
> that situation.
Only if you use the URL modification method!
If you set apt-cacher-ng as "global" proxy in apt.conf settings, it will
also be used for the redirected locations.
Regards,
Eduard.
--
Wenn man alle Gesetze studieren sollte, so hätte man gar keine Zeit,
sie zu übertreten.
-- Johann Wolfgang von Goethe
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
