- From: Roy T. Fielding <fielding@gbiv.com>
- Date: Mon, 23 Sep 2013 18:20:13 -0700
- To: Amos Jeffries <squid3@treenet.co.nz>
- Cc: ietf-http-wg@w3.org
On Sep 15, 2013, at 4:07 AM, Amos Jeffries wrote: > On 14/09/2013 9:30 a.m., Roy T. Fielding 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? > > Consider an ICAP content filter being applied to PUT and POST. In such situation it is useful to append Warning about transformation, etc. > > I don't see how there is any more (or less) difference to Warning on requests as for responses. There are extension warnings possible that could apply to requests. > > Amos Okay, I have left it as is. ....Roy
Received on Tuesday, 24 September 2013 01:20:35 UTC