title: Google Chrome browser issue : reset/clear cache
body: <p>I've already researched this issue extensively on google, and such.</p>
  
  <p>Here it is :  the google chrome browser does not automatically load new web-pages;  instead, it loads old ones.</p>
  
  <p>I did not much bother with this.......until I started coding.</p>
  
  <p>The funny thing is :  I didn't even realize that the chrome-browser was the culprit behind most of the situations when my PHP/HTML code did not work !  I would spend HOURS writing and re-writing code; when I tested it, it would give me the same "old" output.  </p>
  
  <p>It was purely by accident that, one fine day, I decided to completely clear out my chrome cache (clear my broswer data).............and, when I tested some "old" code, it gave me a "new" result !!!!</p>
  
  <p>Imagine my amazement.</p>
  
  <p>From that day onwards, I developed the very irritating, annoying, but necessary, habit of clearing out my browser-cache <strong>EACH TIME</strong> I made changes to my code. </p>
  
  <p>My code is currently progressing rapidly, and I am becoming more irritated with having to refresh my cache each time I want to test new code. Hence, I've made the decision to quit google-chrome, and switch to Mozilla. </p>
  
  <p>Upon doing some research, though, the only reference to this problem was found here :</p>
  
  <p><a href="https://productforums.google.com/forum/#!topic/chrome/xR-6YAkcASQ" rel="nofollow">https://productforums.google.com/forum/#!topic/chrome/xR-6YAkcASQ</a></p>
  
  <p>The solution put forward is the one I employed from the start, after I first noticed this problem.</p>
  
  <p>Apparently, there seems to be no other solution.</p>
  
  <p>So, why am I writing this post, then??   Well, it's quite simple :  the reason I am posting here is in the hope that........maybe.......someone knows of another way around this --- perhaps, something that can be injected into one's code (or, perhaps, within the past year, or month, or week, or even within the past 24 hours, Google has somehow had a much-needed "brainwave", and finally fixed this problem !!)</p>