Hi Nathan,
what's happening is that Azure uses a CDN for custom domains that has its own caching layer separate from your staticwebapp.config rules. Even with "no-cache" headers, the edge nodes might be serving stale content.
add a query string parameter to your URLs when testing. Something like ?v=2 or ?timestamp=123456789 can bypass the CDN cache for immediate verification that your new content is actually deployed.
You can also try forcing a different cache behavior by modifying your staticwebapp.config. Instead of just "no-cache", try:
{ "headers": [ { "path": "**", "headers": [ { "name": "Cache-Control", "value": "no-cache, no-store, must-revalidate" } ] } ] }
The Static Web Apps documentation mentions cache behavior for custom domains https://free.blessedness.top/en-us/azure/static-web-apps/configuration.
Another workaround is to temporarily switch your custom domain to point directly to your .azurestaticapps.net URL instead of using the CDN endpoint. This isn't ideal for production, but it can confirm whether the issue is specifically with the CDN caching.
If you need immediate resolution and have paid support, you should be able to create a support ticket through the Azure portal. Go to your Static Web App resource, then select "Help + support" in the left menu, and create a new support request. Choose "Technical" for issue type and "Static Web Apps" for the service.
You can also try reaching out to the Azure Static Web Apps product team through their GitHub repository. They're often responsive to caching issues reported there.
For future deployments, consider implementing cache-busting techniques in your build process, like adding content hashes to your filenames or using versioned directories
regards,
Alex
and "yes" if you would follow me at Q&A - personaly thx.
P.S. If my answer help to you, please Accept my answer