FAQ

Cache - A dynamic part of my site isn’t updating after user interaction, or changes I have implemented in site development are not yet visible!

The cause of such issues is very likely to be that the site is cached on the Cloudflare edge, or even your browser, and you are seeing the cached version.

Solving caching problems can be done in more than one way, so choose the one that fits you the best.

Let us know which paths and parts of the site are prone to change frequently, so we can permanently configure them to not be cached - until you tell us otherwise.

You can receive an API command from us to use to purge the cache for the zone/domain you are managing or developing. (To be used in Linux/Mac terminal, on Windows please install and use WSL (Windows Subsystem for Linux)

You can get your zone ID from us, or if you are an admin on the Cloudflare dashboard, by looking in the overview of the domain on the Cloudflare dashboard. The same applies to the scoped API token.

If you have access and admin privileges on the Cloudflare dashboard, you can perform a “purge everything” in Caching > Configuration > Purge Everything.

When Development Mode is on, all requests will be passed to the origin server. This allows requests for your website to temporarily bypass our cache so you can verify changes made to cached content.

This is useful when you need to see changes right away. Once enabled, Development Mode lasts for three hours and then turns off automatically.

Note: Unless you are making major changes to your website, we recommend using the Purge Individual Files option ("Custom Purge" in Caching > Configuration, the button above "Purge Everything") instead of turning on Development Mode. This is because Development Mode will cause all requests to go to your origin server, and increased requests to your origin server will temporarily raise your bandwidth and CPU usage.