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

Re: #296: 203 Non-Authoritative Information: deprecate?

From: Julian Reschke <julian.reschke@gmx.de>
Date: Sat, 18 Jun 2011 17:40:17 +0200
Message-ID: <4DFCC6E1.7010604@gmx.de>
To: Mark Nottingham <mnot@mnot.net>
CC: httpbis Group <ietf-http-wg@w3.org>, Roy Fielding <fielding@gbiv.com>
On 2011-06-07 14:04, Julian Reschke wrote:
> On 2011-05-31 10:08, Mark Nottingham wrote:
>> Agreed on both counts. Now #296:
>> http://trac.tools.ietf.org/wg/httpbis/trac/ticket/296
>
> OK, proposed patch at
> <http://trac.tools.ietf.org/wg/httpbis/trac/attachment/ticket/296/296.diff>.
>
>
> The new text would be:
>
> 8.2.4. 203 Non-Authoritative Information
>
> The representation in the response has been transformed or otherwise
> modified by a transforming proxy (Section 2.3 of [Part1]). Note that
> the behaviour of transforming intermediaries is controlled by the no-
> transform Cache-Control directive (Section 3.2 of [Part6]).
>
> This status code is only appropriate when the response status code
> would have been 200 (OK) otherwise. When the status code before
> transformation would have been different, the 214 Transformation
> Applied warn-code (Section 3.6 of [Part6]) is appropriate.
>
> Caches MAY use a heuristic (see Section 2.3.1.1 of [Part6]) to
> determine freshness for 203 responses.
>
> ...and the Changes section would state:
>
> Broadened the definition of 203 (Non-Authoritative Information) to
> include cases of payload transformations as well. (Section 8.2.4)
>
> Best regards, Julian

OK, can we go back discussing this concrete change?

Best regards, Julian
Received on Saturday, 18 June 2011 15:40:58 GMT

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