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

Re: #231: Considerations for new headers

From: Willy Tarreau <w@1wt.eu>
Date: Thu, 30 Jun 2011 10:48:30 +0200
To: Poul-Henning Kamp <phk@phk.freebsd.dk>
Cc: Julian Reschke <julian.reschke@gmx.de>, Mark Nottingham <mnot@mnot.net>, httpbis Group <ietf-http-wg@w3.org>
Message-ID: <20110630084830.GC27687@1wt.eu>
On Thu, Jun 30, 2011 at 07:52:38AM +0000, Poul-Henning Kamp wrote:
> In message <4E0C2885.1090702@gmx.de>, Julian Reschke writes:
> >On 2011-06-30 09:37, Poul-Henning Kamp wrote:
> >> In message<70295C66-3411-4AF7-83E8-775851DACCFB@mnot.net>, Mark Nottingham wri
> >> tes:
> >>> <http://trac.tools.ietf.org/wg/httpbis/trac/ticket/231>
> >>>
> >>> Proposal:
> >>
> >>> Authors of new header fields are advised to consider documenting:
> >>
> >> * How the header field impacts caching.
> >
> >Can a new header field affect caching?
> 
> If not, we should say so.
> 
> ...not that I think that will have any effect.

I agree with PHK here. For instance if some sensitive headers are added
that must not be cached, we should probably add provisions for being able
to do so (just as we have "Cache-control: no-cache=set-cookie").

Regards,
Willy
Received on Thursday, 30 June 2011 08:49:09 GMT

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