If dynamic acceleration is enabled, you can create custom acceleration rules for static and dynamic content. In this case, static content is cached on edge nodes and requests for dynamic content are redirected to the origin server over the optimal route. If dynamic acceleration is disabled, the acceleration for dynamic content delivery becomes unavailable, but static content is still cached on edge nodes.

The following table lists the operations that you can perform to configure acceleration rules for static and dynamic content delivery.
Operation Description
Configure static file types Allows you to configure acceleration rules for static content by specifying the types of files that can be cached on edge nodes. This prevents static content from occupying resources that are reserved for the acceleration of dynamic content delivery.
Specify static file URIs Allows you to configure acceleration rules for static content by specifying the Uniform Resource Identifiers (URIs) of files that can be cached on edge nodes. This prevents static content from occupying resources that are reserved for the acceleration of dynamic content delivery.
Specify static file paths Allows you to configure acceleration rules for static content by specifying the paths of files that can be cached on edge nodes. This prevents static content from occupying resources that are reserved for the acceleration of dynamic content delivery.
Configure back-to-origin requests to retrieve dynamic content Allows you to configure dynamic content retrieval settings, including the protocol used by the client to retrieve dynamic content from the origin server and whether to enable load balancing. You can configure the settings based on your business requirements.