p1/p2: 203 Non-Authoritative Information

Mark Nottingham <mnot@mnot.net> Tue, 23 April 2013 06:03 UTC

Resent-Date: Tue, 23 Apr 2013 06:02:47 +0000
Resent-Message-Id: <E1UUWJT-0002Jr-TH@frink.w3.org>
From: Mark Nottingham <mnot@mnot.net>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Message-Id: <3D1F7A72-16E6-44A5-91DB-650032E55F9C@mnot.net>
Date: Tue, 23 Apr 2013 16:02:18 +1000
To: "ietf-http-wg@w3.org Group" <ietf-http-wg@w3.org>
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Received-SPF: pass client-ip=216.86.168.183; envelope-from=mnot@mnot.net; helo=mxout-08.mxes.net
Subject: p1/p2: 203 Non-Authoritative Information
Archived-At: <http://www.w3.org/mid/3D1F7A72-16E6-44A5-91DB-650032E55F9C@mnot.net>
Resent-From: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list

We define 203 in p2 as being applicable when the content has been modified by an intermediary;

> The 203 (Non-Authoritative Information) status code indicates that the request was successful but the enclosed payload has been modified from that of the origin server's 200 (OK) response by a transforming proxy (Section 5.7.2 of [Part1]). This status code allows the proxy to notify recipients when a transformation has been applied, since that knowledge might impact later decisions regarding the content. For example, future cache validation requests for the content might only be applicable along the same request path (through the same proxies).

However, 203 isn't mentioned anywhere in <https://svn.tools.ietf.org/svn/wg/httpbis/draft-ietf-httpbis/latest/p1-messaging.html#message.transformations>. It seems like it should either be mentioned as an appropriate thing to use there, or deprecated.


--
Mark Nottingham   http://www.mnot.net/

p1/p2: 203 Non-Authoritative Information Mark Nottingham