When you need to fetch the latest static resources to your client, you can enable the development mode. After you enable the development mode, static resource requests are redirected to the origin server. This allows requests to your website to temporarily bypass the caching components of Edge Security Acceleration (ESA) so that you can verify changes to the cached content.
Unless you have made major changes to your website, we recommend that you use the purge cache feature instead of enabling the development mode.
In the development mode, static resource requests are redirected to the origin server, which significantly increases the bandwidth and CPU usage of the origin server and generates additional origin traffic.
The development mode has a higher priority than cache rules.
Once enabled, the development mode lasts for 3 hours and then is automatically disabled. Disable the development mode after debugging to reduce the load on the origin server.
Scenarios
The feature is designed for debugging the access effects of static resource requests.
When you disable the development mode, static resource requests are affected by the cache on the points of presence (POPs) and the caching policies deployed on ESA. This means requests may be served from cached data.
When you enable the development mode, static resource requests bypass the cache components of ESA POPs and access the origin server. This helps you compare the effects of accessing resources from the origin server versus the cache.
Enable the development mode
In the ESA console, choose Websites. In the Website column, click the target website.
In the left navigation pane, choose .
Turn on Development Mode.
