- From: Roland Zink <roland@zinks.de>
- Date: Thu, 02 Oct 2014 18:34:03 +0200
- To: ietf-http-wg@w3.org
I think this didn't changed since RFC 2616 already says:
14.9.5 No-Transform Directive
no-transform
Implementors of intermediate caches (proxies) have found it useful
to convert the media type of certain entity bodies. A non-
transparent proxy might, for example, convert between image
formats in order to save cache space or to reduce the amount of
traffic on a slow link.
Serious operational problems occur, however, when these
transformations are applied to entity bodies intended for certain
kinds of applications. For example, applications for medical
imaging, scientific data analysis and those using end-to-end
authentication, all depend on receiving an entity body that is bit
for bit identical to the original entity-body.
Therefore, if a message includes the no-transform directive, an
intermediate cache or proxy MUST NOT change those headers that are
listed in section 13.5.2 as being subject to the no-transform
directive. This implies that the cache or proxy MUST NOT change
any aspect of the entity-body that is specified by these headers,
including the value of the entity-body itself.
On 02.10.2014 18:20, Smith, Kevin, (R&D) Vodafone Group wrote:
>>> Rightfully. This is what RFC 7230 already requires.
> Why rightfully, though? The example given has merit, and could make the difference between a functional user experience, and not.
>
> Ideally the content server would be providing a response that was suitable for the delivery context, in which case no-transform should indeed be ignored, but that's not always the case in practice. Hence the point about allowing the user to choose.
>
> Cheers
> Kevin
>
>
>
Received on Thursday, 2 October 2014 16:34:27 UTC