Application Acceleration is an Edge Application module that speeds up web applications and APIs through protocol optimizations and manages dynamic content requirements.
With Application Acceleration, you can:
- Create advanced rules in Rules Engine for the request and response phases.
- Customize cache policies for dynamic content based on cookies or query strings through the Advanced Cache Key.
- Enable support and cache of HTTP methods for your edge application.
- Customize CDN cache TTL to values under 60 seconds.
ImplementationSection titled Implementation
|Available cache settings
|Creating a cache setting
|How to configure cache policies for Edge Application
|Configuring Rules Engine
|Creating Request and Response rules using Rules Engine for Edge Application
|Configuring Advanced Cache Key
|How to configure Advanced Cache Key for Edge Application
Advanced Cache KeySection titled Advanced Cache Key
By default, Azion considers each URL as a distinct object in cache. The Advanced Cache Key feature allows you to create advanced cache rules based on two options: Cache by Query Strings and Cache by Cookies. If needed, you can use both options simultaneously to define the content segmentation of your application.Learn more about Advanced Cache Key
Rules EngineSection titled Rules Engine
Application Acceleration enables new options and configurations in Rules Engine, allowing you to customize your application’s business rules. See the full list of variables and list of behaviors to know more.Learn more about Rules Engine
Support for HTTP methodsSection titled Support for HTTP methods
You can expand the supported HTTP methods beyond the native
HEAD methods for your edge applications. By enabling this feature, you’ll gain the ability to utilize the
DELETE HTTP methods in your applications.
By default, Azion’s edge caching is configured to cache only
HEAD requests. However, by enabling this module, you have the option to extend caching to include
OPTIONS requests as well. This allows you to optimize the performance and efficiency of your applications, especially for frequently accessed or data-intensive endpoints that use these HTTP methods.