title: Ajax + pushState bug in Chrome
body: <p>I've encountered a strange bug in Chrome 19. I implemented a full-AJAX website (every non-external link is opened via AJAX request) with pushState support. I transmit the HTML snippets in AJAX via JSON format.</p>
  
  <p>When I leave my site via an external link and then go back, Chrome renders cached data for that URL - the problem is, he caches the JSON content and shows that, instead of full web-page.</p>
  
  <p>This is reproducible by these steps (<strong>UPDATE: I removed AJAX functionality on my website since then, so this bug does no longer appear</strong>):</p>
  
  <ol>
  <li>Open <a href="http://beta.mirtes.cz/" rel="nofollow">http://beta.mirtes.cz/</a></li>
  <li>Click on the second date link (16. 6. 2012 next to "It all began with a strange e-mail"). This page (you are now at <a href="http://beta.mirtes.cz/it-all-began-with-a-strange-e-mail" rel="nofollow">http://beta.mirtes.cz/it-all-began-with-a-strange-e-mail</a>) is loaded via AJAX.</li>
  <li>Click on "It all began with a strange e-mail". You are redirected to an external website.</li>
  <li>Click "Back" in Chrome after the page is completely loaded.</li>
  </ol>
  
  <p>I try to send all AJAX responses with Cache-Control: no-cache, but with no effect.</p>
  
  <p>Firefox 12 works OK.</p>