title: JSON breaking back button in Chrome, Reload Button in IE (Showing as naked data)
body: <p>Before Anything: <a href="https://stackoverflow.com/questions/2037295/getjson-back-button-showing-json-return-data-not-the-page">$.getJSON  back button showing JSON return data not the page</a> did not help, as well as <a href="https://groups.google.com/group/angular/browse_thread/thread/3787ad609c0beb77/eb1b57069dab9f63" rel="nofollow noreferrer">https://groups.google.com/group/angular/browse_thread/thread/3787ad609c0beb77/eb1b57069dab9f63</a> did not and the internet too did not help.</p>
  
  <p>Here's the issue: </p>
  
  <p>I'm calling an url from within a page to get json data, which then gets rendered with jquery templating inside this same page.</p>
  
  <p>Imagine we're on the page <a href="http://someurl.com/search" rel="nofollow noreferrer">http://someurl.com/search</a> and we're starting a request like this</p>
  
  <pre><code>$.ajax({
    url: '/searchthis', //important, this is NOT THE SAME URL
    cache: false,
    type: 'GET',
    headers: {
      "Accept": "application/json",
    },
    dataType: 'json'
    success: function(data) {
      doSomethingWithResults(data);
    }
  });
  </code></pre>
  
  <p>The Rack response has the cache control header set to no cache:</p>
  
  <pre><code>Cache-Control:no-cache
  </code></pre>
  
  <p>Everything works fine, but if you leave the page for another page in Chrome and then press the back button, you will get shown naked JSON Data. The same behaviour is there when you hit the reload Button in IE8. Both work perfectly fine if you just press Enter on the url in the adress bar.</p>
  
  <p>I'm not getting how I could fix this, because the Chrome guys won't do it (see <a href="http://code.google.com/p/chromium/issues/detail?id=108425" rel="nofollow noreferrer">http://code.google.com/p/chromium/issues/detail?id=108425</a>)</p>
  
  <p>It seems to me like misinterpretation on the browsers side, because it caches something it really should not (response Header) and it caches something under a wrong url (because the JSON request does not hit the same URL)</p>