Re: p4-conditional proofreading

• From: Barry Leiba <barryleiba.mailing.lists@gmail.com>
• Date: Mon, 1 Feb 2010 09:33:44 -0500
• To: Julian Reschke <julian.reschke@gmx.de>
• Cc: Anthony Bryan <anthonybryan@gmail.com>, HTTP Working Group <ietf-http-wg@w3.org>
• Message-ID: <9abf48a61002010633j39e608aen2804513260ffa67a@mail.gmail.com>

> Here's an alternative proposal; reverse the sentences so that the BCP14
> keyword comes first (like in the previous list about servers):
>
>  HTTP/1.1 clients:
>
>  o  MUST use that entity tag in any cache-conditional request (using
>     If-Match or If-None-Match) if an entity tag has been provided by
>     the origin server.
>
>  o  SHOULD use that value in non-subrange cache-conditional requests
>     (using If-Modified-Since) if only a Last-Modified value has been
>     provided by the origin server.
>
>  o  MAY use that value in subrange cache-conditional requests (using
>     If-Unmodified-Since) if only a Last-Modified value has been
>     provided by an HTTP/1.0 origin server.  The user agent SHOULD
>     provide a way to disable this, in case of difficulty.
>
>  o  SHOULD use both validators in cache-conditional requests if both
>     an entity tag and a Last-Modified value have been provided by the
>     origin server.  This allows both HTTP/1.0 and HTTP/1.1 caches to
>     respond appropriately.

That's a fine re-write, and I'm mostly happy with it.  May I make a
small edit?  In order to avoid people wondering whether "that value"
refers back to the previous bullet, how's this?:

  HTTP/1.1 clients:

  o  MUST use the entity tag in any cache-conditional request (using
     If-Match or If-None-Match) if an entity tag has been provided by
     the origin server.

  o  SHOULD use the Last-Modified value in non-subrange cache-conditional
     requests (using If-Modified-Since) if only a Last-Modified value has been
     provided by the origin server.

  o  MAY use the Last-Modified value in subrange cache-conditional requests
     (using If-Unmodified-Since) if only a Last-Modified value has been
     provided by an HTTP/1.0 origin server.  The user agent SHOULD
     provide a way to disable this, in case of difficulty.

  o  SHOULD use both validators in cache-conditional requests if both
     an entity tag and a Last-Modified value have been provided by the
     origin server.  This allows both HTTP/1.0 and HTTP/1.1 caches to
     respond appropriately.


Barry

Received on Monday, 1 February 2010 14:34:19 UTC