# Add \`Cache-Control "no-transform"\` HTTP header

**URL:** <https://meta.discourse.org/t/add-cache-control-no-transform-http-header/25152>\
**Category:** Feature\
**Created:** [February 12, 2015, 6:54am UTC](https://meta.discourse.org/t/add-cache-control-no-transform-http-header/25152 "2015-02-12T06:54:35Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![DeanMarkTaylor](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/deanmarktaylor/32/102462_2.png) [@DeanMarkTaylor](https://meta.discourse.org/u/DeanMarkTaylor)\
**Post date:** [February 15, 2015, 4:07am UTC](https://meta.discourse.org/t/add-cache-control-no-transform-http-header/25152/4 "2015-02-15T04:07:23Z")

</div>

In Vodafone the 2nd largest UK mobile network carrier (in terms of revenue) does indeed modify the page to include the failing JavaScript and also does respect the no-transform header.

Actually a Vodafone employee wrote the initial draft and was an editor for the [W3C Content Transformation Landscape Working Group Note in 2007](http://www.w3.org/TR/ct-guidelines/) which outlines Content Transformation proxies handling things like this.

And obviously the [HTTP spec mandates](http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.9.5) how a proxy server MUST handle the `no-transform` header.

Sadly this is not “ethically bizarre” this is “normal” and within spec except for where a `no-transform` header is included, then a proxy “MUST NOT” transform the data.

---

_[View the full topic](https://meta.discourse.org/t/add-cache-control-no-transform-http-header/25152)._