W3C home > Mailing lists > Public > ietf-http-wg@w3.org > July to September 2013

Re: use of Warning in request messages

From: Mark Nottingham <mnot@mnot.net>
Date: Tue, 17 Sep 2013 10:59:53 +1000
Cc: IETF HTTP WG <ietf-http-wg@w3.org>
Message-Id: <F1165320-919F-43FB-A3C3-82C24BB5D343@mnot.net>
To: Roy T. Fielding <fielding@gbiv.com>

On 14/09/2013, at 7:30 AM, Roy T. Fielding <fielding@gbiv.com> wrote:

> When editing the definition of Warning last night, I noticed
> that it claims to be applicable to both request and response
> messages.  That is surprising (and not in a good way).
> 
> I don't see how sending Warning in a request would ever be useful.
> At best, it might mistakenly be stored in a PUT.
> 
> Does anyone know?  Can I make Warning specific to responses?


2616 said:

> Warning headers can in general be applied to any message, however some specific warn-codes are specific to caches and can only be applied to response messages.

The case that I can think of is a non-transparent intermediary changing a request payload. 

*shrug*

Cheers,


--
Mark Nottingham   http://www.mnot.net/
Received on Tuesday, 17 September 2013 01:00:24 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:15 UTC