Updates appear on Custom Domain 1 hour after a change, but appear on the xxxx.azurewebsites.net iimmediately

Antony Cook 1 Reputation point
2021-10-03T20:42:06.83+00:00

I have deployed a wordpress site as an App Service (using the container on Marketplace ) and created a DNS Zone for use with my custom domain (registered with GoDaddy).

Let's say the custom domain is abc.co.uk and the App Service is abc-uk.azurewebsites.net

When I make a change to the site, whether that's styling or content, and go the custom domains URL, the changes do not appear until around 1 hr after I make them however if I browse to abc-uk.azurewebsites.net I see them immediately. This is particularly troublesome with a website that accepts bookings (the number of places available is not decrementing immediately on the custom domains URL but I can see them correct on the azurewebsites.net URL).

Verified also using curl via the portal shell in case it was caching outside of the Azure network. Curl against azurewebsites shows the most up to date content, Curl against the custom domains URL shows it out of date.

I don't have CDN or Front Door configured...it's just basic configuration.

So where is the caching happening and how to I stop it/configure it!

Also note, if I restart the app service, the custom domains URL then shows up to date content but this isn't a Wordpress/deployment issue as I can see the two different versions simultaneously by browsing to both 2 URLs.

Azure App Service
Azure App Service
Azure App Service is a service used to create and deploy scalable, mission-critical web apps.
6,823 questions
{count} votes

1 answer

Sort by: Most helpful
  1. Ryan Hill 25,476 Reputation points Microsoft Employee
    2021-11-10T19:56:41.737+00:00

    Hi @Antony Cook , glad to see that your issue was resolved offline.

    For the benefit of the greater community, WordPress image by default uses fastcgi caching and can be resolved by either restarting the app service or modifying the config file located in /home/etc/ngix. In this instance, caching was disabled server side through file configuration and a WordPress caching plugin used to improve performance.

    0 comments No comments