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: Wed, 08 Jun 2011 13:25:11 +0200
Message-ID: <4DEF5C17.1030804@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:14, Mark Nottingham wrote:
> +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.
> ...

Like this...?

    An HTTP-to-HTTP proxy is called a "transforming proxy" if it is
    designed or configured to modify request or response messages in a
    semantically meaningful way (i.e., modifications, beyond those
    required by normal HTTP processing, that change the message in a way
    that would be significant to the original sender or potentially
    significant to downstream recipients).  For example, a transforming
    proxy might be acting as a shared annotation server (modifying
    responses to include references to a local annotation database), a
    malware filter, a format transcoder, or an intranet-to-Internet
    privacy filter.  Such transformations are presumed to be desired by
    the client (or client organization) that selected the proxy and are
    beyond the scope of this specification.  However, when a proxy is not
    intended to transform a given message, we use the term "non-
    transforming proxy" to target requirements that preserve HTTP message
    semantics.  See Section 8.2.4 of [Part2] and Section 3.6 of [Part6]
    for status and warning codes related to transformations.

(last sentence added: see also 
<http://trac.tools.ietf.org/wg/httpbis/trac/attachment/ticket/296/296.diff>).

Best regards, Julian
Received on Wednesday, 8 June 2011 11:26:02 GMT

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