title: How to refresh ASPX page and Javascript code that has been cached by proxy service
body: <p><strong>The Issue</strong></p>
  
  <p>Recently, I deployed a page to production containing javascript which used setInterval() to ping a webservice every few seconds. The behavior can be summed up as follows:</p>
  
  <p>Every X seconds, Javascript on the upcomingEvents.aspx page calls the hitWebService() function, which sits in the hitWebService.js file.</p>
  
  <p>The X interval value set proved to be too small, so, I removed all references to hitWebService(), the hitWebService.js file itself, and the web service it was trying to reach.</p>
  
  <p>Attempts to hit the web service from normal IP addressess dropped off, but I am still getting attempted hits from a number of users who use a proxy service.</p>
  
  <p>My theory is that my upcomingEvents.aspx and hitWebService.js have been cached by the proxy service. Indeed, when I log the referrer strings when a user hits  the error page (every so often, one of these users will get redirected here), they are being referred from upcomingEvents.aspx.</p>
  
  <p>The issue is that the attempts to hit this web service are filling up the IIS logs at an uncomfortable rate, and are causing unnecessary traffic on the server.</p>
  
  <p><strong>What I have attempted</strong></p>
  
  <ul>
  <li>Removed web service completely</li>
  <li>Deleting the hitWebService.js file, also replaced it with dummy file</li>
  <li>Changed content expiration on IIS so that content expires immediately</li>
  <li>Added Response.Cache.SetCacheability(HttpCacheability.NoCache) to the .vb codebehind on page</li>
  <li>Completely republished site with changes</li>
  <li>Restarted IIS, stopped and started IIS.</li>
  </ul>
  
  <p><strong>Interesting bits</strong></p>
  
  <ul>
  <li>I can alter the vb codebehind on UpcomingEvents.apsx to log session details, etc, and it seems to update almost instantly for the proxy service users</li>
  </ul>
  
  <p><strong>The Question</strong></p>
  
  <p>If my theory is correct, and the proxy server is indeed caching these the files hitWebService.js and upcomingEvents.aspx, are there any other routes that I can go down to force a code refresh, considering the above strategies haven't worked? </p>
  
  <p>Thanks a lot,</p>