W3C home > Mailing lists > Public > ietf-http-wg@w3.org > April to June 2011

Re: Clarifying Pragma's introduction

From: Roy T. Fielding <fielding@gbiv.com>
Date: Wed, 4 May 2011 16:15:18 -0700
Cc: HTTP Working Group <ietf-http-wg@w3.org>
Message-Id: <0FAA0768-6B69-4044-B963-CFFEF1A20ABB@gbiv.com>
To: Mark Nottingham <mnot@mnot.net>
On May 4, 2011, at 3:27 AM, Mark Nottingham wrote:

> <http://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-14#section-3.4>
> 
> The intro for Pragma currently says:
> 
>   The "Pragma" header field is used to include
>   implementation-specific directives that might apply to any recipient along
>   the request/response chain. All pragma directives specify optional behavior
>   from the viewpoint of the protocol; however, some systems &MAY; require
>   that behavior be consistent with the directives.
> 
> Since adding new pragma directives is deprecated, this doesn't make much sense any more.
> 
> Any objection to rewriting the paragraph above as:
> 
>  The "Pragma" header field allows backwards compatibility with HTTP/1.0
>  caches, so that clients can specify a "no-cache" request that they will understand
>  (as Cache-Control was not defined until HTTP/1.1). 
> 
>  In HTTP/1.0, it was defined as an extensible field for implementation-specified directives
>  for recipients. This specification deprecates such extensions to improve interoperability.

+1 if s/it/Pragma/;

....Roy
Received on Wednesday, 4 May 2011 23:15:42 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:51:40 GMT