Edge Security Acceleration:Purge cache by URL with parameters ignored

Scenarios

File version control

• Description: Your website has a large number of static resources, such as images, CSS files, and JavaScript files. The URLs of these resources carry different query parameters that can be helpful with version and cache control. Each time you update the resources, you want to ensure that the related cache is invalidated immediately. This enables users to fetch the most recent version of the resources.

• Example: The following URLs link to two different versions of the same file.

  • https://www.example.com/assets/style.css?v=1

  • https://www.example.com/assets/style.css?v=2

• Solution: Submit the URL without query parameters, such as https://www.example.com/assets/style.css, to clear the cache of all versions of the file.

Image processing

• Description: Your website may generate various images in response to different query parameters, such as thumbnails and images in different sizes. To ensure these images are updated and served immediately after processing, you need to clear the related cache.

• Example: The following URLs link to an image in two different sizes.

  • https://www.example.com/images/photo.jpg?size=small

  • https://www.example.com/images/photo.jpg?size=medium

• Solution: Submit the URL without query parameters, such as https://www.example.com/images/photo.jpg, to clear the cache for all versions that are generated with different parameters.

Purge cache by URL with parameters ignored

1. In the ESA console, choose Websites and click the name of the website you want to manage.

2. In the left-side navigation pane, choose Cache > Purge Cache.

3. On the Purge Cache tab, configure the purge settings.

   • Type: Select By URL with Parameters Ignored.

   • Input Method: Select Manual Input or Upload File.

     • Manual Input

       Enter one or more URLs that do not include request parameters. One URL per line. You can submit up to 100 URLs at a time. Example:

       https://www.example.com/cat.jpg
       https://www.example.com/image/cat.jpg

     • Upload File

       If a large number of URLs need to be purged, you can specify the URLs in a TXT file and then upload the file for batch purging. One URL per line. The size of the TXT file cannot exceed 10 MB.

   • Purge Method: Select Mark as Expired or Delete.

     • Mark as Expired

       If the requested content is one of the resources that you submit to purge, the nearest POP checks the Last-Modified parameter of the resource on the origin server. If the parameter value is the same as that of the cached resource, the POP serves the cached resource. Otherwise, the cached resource is considered expired. In this case, the POP fetches the latest version from the origin server, delivers it to the client, and updates the cache with the new version.

     • Delete

       If the requested content is one of the resources that you submit to purge, the nearest POP fetches the latest version from the origin server, delivers it to the client, and updates the cache with the new version.

   

4. Click Submit.

5. View the purge progress.

   • You can view the progress and details of a purge task on the Purge Records tab. The purge task is complete when the progress reaches 100%. The duration varies based on the number of objects that you want to purge.

   • If you select Upload File for purging, you can view the upload status on the Upload Records tab. After the file is uploaded, the purge task starts. You can view the purging status of each file on the Purge Records tab.

     

Availability