title: Any reason not to add "Cache-Control: no-transform" header to every page?
body: <p>We have recently fixed a nagging error on our website similar to the one described in <a href="https://stackoverflow.com/questions/4113268/how-to-stop-javascript-injection-from-vodafone-proxy">How to stop javascript injection from vodafone proxy?</a> - basically, the Vodafone mobile network was vandalizing our pages in transit, making edits to the JavaScript which broke viewmodels.</p>
  
  <p>Adding a "Cache-Control: no-transform" header to the page that was experiencing the problem fixed it, which is great.</p>
  
  <p>However, we are concerned that as we do more client-side development using JavaScript MVP techniques, we may see it again.</p>
  
  <p>Is there any reason not to add this header to every page served up by our site?</p>
  
  <p>Are there any <em>useful</em> transformations that this will prevent? Or is it basically just similar examples of carriers making ham-fisted attempts to minify things and potentially breaking them in the process?</p>