W3C home > Mailing lists > Public > ietf-http-wg-old@w3.org > September to December 1996

Re: 13.1.2 Warnings

From: Ben Laurie <ben@gonzo.ben.algroup.co.uk>
Date: Thu, 17 Oct 1996 19:37:32 +0100 (BST)
To: Ari Luotonen <luotonen@netscape.com>
Cc: masinter@parc.xerox.com, http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com
Message-Id: <9610171937.aa14412@gonzo.ben.algroup.co.uk>
Ari Luotonen wrote:
> 
> 
> > - HTTP/1.1 & digest:
> >    Expecting RFC Real Soon Now.
> >    Complaints, editorial advice, ambiguities welcome.
> 
> 13.1.2 Warnings says:
> 
>     ...
>     Warnings are always cachable, because they never weaken the transparency
>     of a response. This means that warnings can be passed to HTTP/1.0 caches
>     without danger; such caches will simply pass the warning along as an
>     entity-header in the response.
>     ...
> 
> This is not right.  HTTP/1.0 cache will cache this header, and the
> Warning will remain in the cache file even if the entity is up-to-date
> checked later.  So clients could e.g. see a warning saying that the
> response may be stale even if the proxy just did an up-to-date check
> and it was ok.

Wouldn't that mean that the HTTP/1.0 cache was out-of-date wrt the upstream
cache (and hence would refetch and lose the warning header)? Or am I missing
something?

Cheers,

Ben.

-- 
Ben Laurie                  Phone: +44 (181) 994 6435
Freelance Consultant and    Fax:   +44 (181) 994 6472
Technical Director          Email: ben@algroup.co.uk
A.L. Digital Ltd,           URL: http://www.algroup.co.uk
London, England.            Apache Group member (http://www.apache.org)
Received on Thursday, 17 October 1996 12:42:52 EDT

This archive was generated by hypermail pre-2.1.9 : Wednesday, 24 September 2003 06:32:15 EDT