W3C home > Mailing lists > Public > ietf-http-wg-old@w3.org > January to April 2000

Re: Question for HTTP/1.1 cache implementors (both proxy & client caches)

From: Jeffrey Mogul <mogul@pa.dec.com>
Date: Wed, 19 Apr 2000 16:40:35 -0700
Message-Id: <200004192340.QAA07561@wera.pa.dec.com>
To: http-wg@hplb.hpl.hp.com
"Roy T. Fielding" <fielding@kiwi.ICS.UCI.EDU> writes:
Message-Id:  <200004191602.aa19350@gremlin-relay.ics.uci.edu>

    >   The max-age directive on a response implies that the
    >   response is cacheable (i.e., "public") unless some other, more
    >   restrictive cache directive is also present.  If a more
    >   restrictive cache directive (such as "no-cache" or "no-store")
    >   is present, the cache MUST ignore the max-age directive;
    >   this supports extensibility using the mechanism described
    >   in section 14.9.6.
    Wouldn't that become a contradiction with the extension scheme?
    In other words, that requirement along with your example of
	Cache-Control: no-store, community="UCI", max-age=30

    would require that the recipient ignore max-age even if it did
    understand the community extension.  I think that is why we decided
    to use relative constraints rather than absolute constraints in the
    language above.

No contradiction, because 14.9.6 says:

						Both the new	
   directive and the standard directive are supplied, such that
   applications which do not understand the new directive will default
   to the behavior specified by the standard directive, and those that
   understand the new directive will recognize it as modifying the
   requirements associated with the standard directive.

The key phrase here is that the new directive ("community", in
this example) "[modifies] the requirements associated with the
standard directive."  Presumably, the "modification" needs to
be part of the specification for each extension.

I.e., the specification for "community" could include,
hypothetically, "an implementation that complies with the
specification for the community directive SHOULD ignore the
no-store directive if it appears together with the community
directive."  Which means that the no-store directive, being
ignored, would not take precedence over the max-age directive
for "community-aware" implementations.

Received on Thursday, 20 April 2000 00:41:55 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:40:24 UTC