Hi!

On Sun, 2011-03-20 at 16:45 +0000, Mark Hindley wrote:
> On Sun, Mar 20, 2011 at 05:09:53PM +0100, Eus wrote:
> > 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?
> 
> Yes, I suspect so, but presumably with a 200 status and that would have 
> been returned to the apt-get/aptitude client which would not be happy!
> 
> > 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"?
> 
> Again, I think so. apt-cacher would go into its 'offline' mode and do 
> the best it can with cached files.
> 
> I can't think of a way for me to test either of those scenarios without 
> your setup. Could you do it and check the behaviour is as expected

Sure.

> Could you try this patch as well which should check that the cached 
> status is still valid.

Yup.

BTW, what do you think if apt-cacher simply ignores the cached header
when the cached header does not have status 200?

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

Reply via email to