Hi! On Sun, 2011-03-20 at 17:01 +0100, Eus wrote:
> On Sun, 2011-03-20 at 15:50 +0000, Mark Hindley wrote: > > > > I suspect it appeared as the CURLOPT_FOLLOWLOCATION was not set. > But, if it is possible, I want to have a long-term solution as well. > > What semantic does 404 have in apt-cacher? Does the semantic allow for > not using cached header in case apt-cacher gets 404 referring to the > above scenario where "apt-get update" probes for non-existent files? If suppose CURLOPT_FOLLOWLOCATION was set when the wireless connection had been disconnected, then would apt-cacher have cached the login page of the hotspot provider? If that is the case, will apt-cacher return the cached login page when apt-cacher gets 404 during the normal non-existent file probe of "apt-get update"? Thanks. > > Mark -- Best regards, Eus (FSF member #4445) In this digital era, where computing technology is pervasive, your freedom depends on the software controlling those computing devices. Join free software movement today! It is free as in freedom, not as in free beer! Join: http://www.fsf.org/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
