Azure Static Web app - old verstion still in cache

Question

Azure Static Web app - old verstion still in cache

Hugh Sheehy 1

I've put up several simple static web apps and one in particular keeps reverting to the old version. If I go into Dev tools in a browser and force empty cache and hard reload, the new version comes up. But if i leave dev tools and do a reload, the old version is back.

And not just for me. Even people who have never gone to the page see the old version. The new version does seem to come up, even for me, in incognito sessions.

I've purged the Azure CDN (which i hadn't set to include those pages anyway). No change.

I've looked for the pages on Azure Storage Explorer to see if there's a cache setting I can change, but I can't find any of the sites' html through Azure Storage Explorer.

How the heck do I get the new version to show?

Hugh Sheehy 1 Reputation point

2020-12-14T17:39:05.667+00:00

A week later, we're all still seeing the old version of the app (several versions old now) unless we open dev tools and do cache delete and hard reload.
SnehaAgrawal-MSFT 11,616 Reputation points Microsoft Employee

2020-12-15T08:55:26.68+00:00

Apologize for the late response and inconvenience with this issue! I'm checking on this internally with our product engineering team and will get back to you soon. Thanks for your patience and co-operation in this matter!
SnehaAgrawal-MSFT 11,616 Reputation points Microsoft Employee

2020-12-15T16:47:38.587+00:00

Thanks for asking question! Well the fact that you’ve added an Azure CDN in front adds some complexity.

Probably the easiest way to debug this is to work backwards. If you accesses the site through the default hostname (i.e. red-field-1234) instead of through the cdn, do you still see the issue with the new version not being applied?
Hugh Sheehy 1 Reputation point

2020-12-15T16:49:57.273+00:00

This is the direct link. https://icy-flower-0dfee1e03.azurestaticapps.net/ Still showing me a version from - now - a couple of weeks ago.
I've purged the CDN several times. I could turn it off completely, if that'd help figuring this out.
SnehaAgrawal-MSFT 11,616 Reputation points Microsoft Employee

2020-12-15T17:10:37.097+00:00

Thanks for reply! Could you please try the following test.

If you inspect the traffic when reaching the default hostname, you should see a header in the response (for any file, I chose index.html) like etag: "30060206".

After you push an update you should see this etag header change. If you are still seeing the same content but the etag has changed, then there may be something wrong with your deployments.

Let us know.
Hugh Sheehy 1 Reputation point

2020-12-15T17:11:46.957+00:00

will do. Deployments are straight from github and haven't shown any errors.
Hugh Sheehy 1 Reputation point

2020-12-15T21:40:33+00:00

So as you say, I see etag: "30060206" on the new version. I can only see the etag if i reload the page with dev tools open. But if i have dev tools open i always get the new version. See the video here.

https://www.youtube.com/watch?v=3a4ePWOCzvQ

I did a small change and pushed a change through github. the etag is now etag: "25540746"

And, after a couple of minutes of the same problem, I hit reload one more time and - taTAAAAA - the new version shows.

I have NO idea what's been going on, but it's stopped. Have a look at the video....see at least that I wasn't making it up!

H
Eric 1 Reputation point

2020-12-16T15:10:56.143+00:00

I'm having the same issue with Azure App Service. It's a static Next JS export app. No matter what I seem to do, it shows the old version at first until I press F5. I then close the window, go back in, and it is back to the old one. I've tried adding the following options also:

WEBSITE_LOCAL_CACHE_OPTION = Never
WEBSITE_DYNAMIC_CACHE = 0

and in web.config, added to <StaticContent> to have <clientCache cacheControlMode="DisableCache" />

This is on a "Production P2V2" app service. I've restarted the app service several times as well.
SnehaAgrawal-MSFT 11,616 Reputation points Microsoft Employee

2020-12-17T05:07:59.69+00:00

Thanks a lot for all the effort you put in for debugging this! Could you please confirm if you have inspect open and the “disable cache” box is checked? As then the browser will skip any cached content and pull the new version.

If this is the case, then this confirms that the client is caching old content which is the issue here. And this may be either because of a service worker or header overrides.

Let us know.
SnehaAgrawal-MSFT 11,616 Reputation points Microsoft Employee

2020-12-22T18:09:08.123+00:00

Just checking if you have chance to see above response. Please let us know if issue persists.

Hugh Sheehy 1 Reputation point

2020-12-14T17:39:05.667+00:00

A week later, we're all still seeing the old version of the app (several versions old now) unless we open dev tools and do cache delete and hard reload.
SnehaAgrawal-MSFT 11,616 Reputation points Microsoft Employee

2020-12-15T08:55:26.68+00:00

Apologize for the late response and inconvenience with this issue! I'm checking on this internally with our product engineering team and will get back to you soon. Thanks for your patience and co-operation in this matter!
SnehaAgrawal-MSFT 11,616 Reputation points Microsoft Employee

2020-12-15T16:47:38.587+00:00

Thanks for asking question! Well the fact that you’ve added an Azure CDN in front adds some complexity.

Probably the easiest way to debug this is to work backwards. If you accesses the site through the default hostname (i.e. red-field-1234) instead of through the cdn, do you still see the issue with the new version not being applied?
Hugh Sheehy 1 Reputation point

2020-12-15T16:49:57.273+00:00

This is the direct link. https://icy-flower-0dfee1e03.azurestaticapps.net/ Still showing me a version from - now - a couple of weeks ago.
I've purged the CDN several times. I could turn it off completely, if that'd help figuring this out.
SnehaAgrawal-MSFT 11,616 Reputation points Microsoft Employee

2020-12-15T17:10:37.097+00:00

Thanks for reply! Could you please try the following test.

If you inspect the traffic when reaching the default hostname, you should see a header in the response (for any file, I chose index.html) like etag: "30060206".

After you push an update you should see this etag header change. If you are still seeing the same content but the etag has changed, then there may be something wrong with your deployments.

Let us know.
Hugh Sheehy 1 Reputation point

2020-12-15T17:11:46.957+00:00

will do. Deployments are straight from github and haven't shown any errors.
Hugh Sheehy 1 Reputation point

2020-12-15T21:40:33+00:00

So as you say, I see etag: "30060206" on the new version. I can only see the etag if i reload the page with dev tools open. But if i have dev tools open i always get the new version. See the video here.

https://www.youtube.com/watch?v=3a4ePWOCzvQ

I did a small change and pushed a change through github. the etag is now etag: "25540746"

And, after a couple of minutes of the same problem, I hit reload one more time and - taTAAAAA - the new version shows.

I have NO idea what's been going on, but it's stopped. Have a look at the video....see at least that I wasn't making it up!

H
Eric 1 Reputation point

2020-12-16T15:10:56.143+00:00

I'm having the same issue with Azure App Service. It's a static Next JS export app. No matter what I seem to do, it shows the old version at first until I press F5. I then close the window, go back in, and it is back to the old one. I've tried adding the following options also:

WEBSITE_LOCAL_CACHE_OPTION = Never
WEBSITE_DYNAMIC_CACHE = 0

and in web.config, added to <StaticContent> to have <clientCache cacheControlMode="DisableCache" />

This is on a "Production P2V2" app service. I've restarted the app service several times as well.
SnehaAgrawal-MSFT 11,616 Reputation points Microsoft Employee

2020-12-17T05:07:59.69+00:00

Thanks a lot for all the effort you put in for debugging this! Could you please confirm if you have inspect open and the “disable cache” box is checked? As then the browser will skip any cached content and pull the new version.

If this is the case, then this confirms that the client is caching old content which is the issue here. And this may be either because of a service worker or header overrides.

Let us know.
SnehaAgrawal-MSFT 11,616 Reputation points Microsoft Employee

2020-12-22T18:09:08.123+00:00

Just checking if you have chance to see above response. Please let us know if issue persists.

Answer 1

Lance Coffman 6

anyone have solution here, i also had same issue had to clear cache and hard load to see changes

Azure Static Web app - old verstion still in cache

1 answer

Activity