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

Re: BNF for Cache-Control

From: Julian Reschke <julian.reschke@gmx.de>
Date: Mon, 25 May 2009 08:56:09 +0200
Message-ID: <4A1A4109.2050105@gmx.de>
To: Adrien de Croy <adrien@qbik.com>
CC: HTTP Working Group <ietf-http-wg@w3.org>
Adrien de Croy wrote:
> I guess the answer lies in the wording around the directives 
> themselves.  Some of them it's pretty clear are intended only for 
> request messages, some for response messages.  Some are less clear, and 
> the syntax for some differs between request and response (e.g no-cache).

In case you didn't notice: those have been separated into distinct 
subsections since draft 05.

> So one way to look at this would be that the grouping of directives into 
> cache-request-directive and cache-response-directive are mainly to 
> demonstrate which type of messages these directives are expected to be 
> used in, without banning them from the other.
> 
> I guess a similar issue would arise in any header that could be part of 
> a request or response message which contains directives which may or may 
> not make sense for a request or a response (e.g. Connect).
> 
> In the end, I'm more than happy to ignore headers that don't make sense 
> in the context, but specific wording in the spec to back those decisions 
> up would be useful.

The descriptions already should clearly say "general", "request", 
"response", or "entity"...

Do you think that is not sufficient? Maybe you could clarify, based on a 
concrete example?

BR, Julian
Received on Monday, 25 May 2009 06:57:01 GMT

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