title: Angular index.html cached for some users after base URL changed
body: <p>Here is the story of a version upgrade <strong>blocker</strong>.</p>
  <p>We have an Angular dashboard served by an &quot;Azure App Service Web App&quot;.
  The dashboard communicates with a NodeJS backend, also served by another Azure instance.</p>
  <p>There was until now 2 releases deployed.
  The first dashboard release was accessible through a single URL and contained no internal routes. Let's name the URL &quot;domain.com&quot;
  The second dashboard release added a base-href change to the main URL. And added also internal
  routes. Let's name the result URL &quot;domain.com/base-href/internal-page&quot;</p>
  <p><strong>The problem:</strong>
  When we deployed the release 3, some users discovered that opening the main URL &quot;domain.com&quot; they see the index.html from release 2, and opening the same URL &quot;domain.com&quot; on another tab they get the index.html from release 3. And so on alternatively...</p>
  <p><strong>The verifications we did:</strong>
  There is no service in that Angular dashboard.
  There is no cache configuration set on Azure. To confirm that, we put off completely the Azure service, and the users concerned still saw the index.html (loaded from disk cache) from release 2.</p>
  <p>What could we do now to be as sure as possible that on release 3, there won't be at all (if possible) users seeing the index.html from release 2, loaded from disk cache. If it's not possible, how can we prevent the index.html from release 3 to be cached by Chrome ?</p>