Add the Cache-Key Query String feature to the rule identified in the previous step.If an existing rule does not exist, then you should create one. Identify an existing rule that identifies the set of requests for which query string caching should be enabled.From within Rules Engine, create a draft or duplicate your existing policy.Additionally, it reduces or eliminates unnecessary image processing due to a cache miss. This recommendation ensures optimal performance by allowing our CDN to serve more requests from cache. We recommend that you restrict query string caching to query string parameters that are critical to your business needs. This mode prevents our CDN from serving images that have already been processed by Edge Image Optimizer. We strongly recommend that you avoid setting up query string caching to no-cache mode. Verify that query string caching has not been enabled for images that will be transformed by Edge Image Optimizer. It may take up to an hour to activate Edge Image Optimizer. If Deactivate is already present, then you have previously enabled Edge Image Optimizer and no further action is required. How? From the main menu, navigate to | Edge Image Optimizer. Navigate to the Edge Image Optimizer page.One or more transformation(s) have been requested via: Edge Image Optimizer has been enabled on the request via Rules Engine.Edge Image Optimizer has been activated.Activating and Enabling Edge Image OptimizerĮdge Image Optimizer transforms images when the following conditions are met: Jpg | jpeg | pjpg | pjpeg | png | ppng | webp | tiff | tifĮdge Image Optimizer returns an error when an attempting to generate an image that exceeds the above limits. Images that meet the following requirements are eligible for processing: Restrictions vary according to whether Edge Image Optimizer will process or generate an image. Otherwise, our CDN will apply the requested set of optimizations to the source image, deliver it to the client, and then cache both the source and optimized image. ![]() If the optimized image has been cached, then it will be delivered immediately to the client. Cache increases the speed through which that particular edge server can deliver that asset for subsequent requests. When used in reference to our CDN, it refers to the temporary storage of an asset on an edge server or an origin shield server. Upon receiving a request for an optimized image, our CDN will check whether an image with the requested set of optimizations has been cached Refers to the storage of data to improve data delivery performance. The order in which parameters are defined in the request URL does not affect the order in which they will be applied to the image. For example, the following request URL will resize the source image to 500 x 500 and then apply a blur effect to the resized image:
0 Comments
Leave a Reply. |