After you enable the development mode, all 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. This feature is useful when you want to view changes in real time. Once enabled, the development mode lasts for 3 hours and then is automatically disabled.
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, all requests are redirected to the origin server, which significantly increases the bandwidth and CPU usage of the origin server.
The development mode has a higher priority than cache rules.
Enabling the development mode may significantly increase the origin traffic. Disable the development mode after debugging.
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 to compare the effects of accessing resources from the origin server versus the cache.
Procedure
Log on to the ESA console.
In the left-side navigation pane, click Websites.
On the Websites page, find the website that you want to manage, and click the website name or View Details in the Actions column.
In the left-side navigation pane, choose .
Turn on Development Mode.
