# Add \`Cache-Control "no-transform"\` HTTP header **URL:** \ **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:** 1
**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 12, 2015, 6:54am UTC](https://meta.discourse.org/t/add-cache-control-no-transform-http-header/25152/1 "2015-02-12T06:54:35Z")
Continuing the discussion from [JavaScript Uncaught ReferenceError: bmi\_load is not defined](https://meta.discourse.org/t/javascript-uncaught-referenceerror-bmi-load-is-not-defined/25129/3): Accessing a Discourse site via UK 3G/GPRS providers causes HTML content to be modified and JavaScript errors to be introduced. Adding `Cache-Control "no-transform"` header for HTML results would resolve this. However this might have other ramifications in terms of intermediate caching servers, but as long as this isn’t included on the image files it shouldn’t have that much of an effect other than preventing JavaScript errors. If a site is behind Google PageSpeed - this header would cause the page not to be rewritten, perhaps impacting CloudFlare sites too… personally I would prefer knowing the site is loaded without errors. Personally I have experienced this before non-discourse sites where Google Maps wouldn’t load because the HTML was modified (corrupting valid HTML) and the JavaScript for Google Maps then being unable to read the “key” required in the `.js` file URL. Considering `.js` files are highly optimised by Disourse I would also recommend adding the “no-transform”` HTTP header JavaScript files too, there is no need for them to be modified (“transformed”). --- _[View the full topic](https://meta.discourse.org/t/add-cache-control-no-transform-http-header/25152)._