Edge Security Acceleration:Purge cache by URL (ignore parameters)

Scenarios

File version control

• Description: Your website has static resources such as images, CSS files, and JavaScript files whose URLs carry query parameters for version or cache control. When you update these resources, you need to immediately invalidate the related cache so that users fetch the latest version.

• 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 generates image variants based on query parameters, such as thumbnails or different sizes. After reprocessing, you need to clear the related cache so that updated images are served immediately.

• 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, select Websites, and in the Website column, click the target site.

2. In the navigation pane, select Caching > 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: You can choose between two methods: Mark as Expired and Delete.

     Refresh method	Description
     Mark as Expired	Nodes are processed according to the following flow: The ESA POP sends an origin request with the If-Modified-Since and If-None-Match request headers. The origin server compares the file modification time. If the file is not modified, the origin server returns a 304 status code. The ESA POP can then use the existing cache file to respond to the client request. If the file is modified, the origin server returns a 200 status code and the latest file. The ESA POP returns the latest file to the client and caches the resource.
     Delete	If a user requests content that matches a resource to be refreshed, the ESA POP directly fetches the new resource from the origin, returns it to the user, and caches the new resource.

   

4. Click Submit.

5. View the purge progress.

   • After you submit a purge task, track its progress on the Purge Records tab. 100% indicates completion. Large tasks may take longer.

   • If you select Upload File, check the file execution status on the Upload Records tab. 'Success' means the file was uploaded and the purge task started. Monitor each URL on the Purge Records tab.

     

Availability