- From: Mark Nottingham <mnot@mnot.net>
- Date: Tue, 7 Jun 2011 22:14:23 +1000
- To: Julian Reschke <julian.reschke@gmx.de>
- Cc: httpbis Group <ietf-http-wg@w3.org>, Roy Fielding <fielding@gbiv.com>
+1 from me. At some point it would be nice if the section on transforming intermediaries referred to it and the warn code as well. Cheers, On 07/06/2011, at 10:04 PM, 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 -- Mark Nottingham http://www.mnot.net/
Received on Tuesday, 7 June 2011 12:14:51 UTC