- From: Mark Nottingham <mnot@mnot.net>
- Date: Wed, 22 Jun 2011 10:37:07 +1000
- To: Julian Reschke <julian.reschke@gmx.de>
- Cc: httpbis Group <ietf-http-wg@w3.org>, Roy Fielding <fielding@gbiv.com>
I haven't heard any objection to the change in the status code itself, so I think we can go ahead and incorporate this; discussion about the term "transforming proxy" and the exact constraints on transformation can be separate issues. Cheers, On 19/06/2011, at 1:40 AM, Julian Reschke wrote: > 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 > -- Mark Nottingham http://www.mnot.net/
Received on Wednesday, 22 June 2011 00:37:34 UTC