All Products
Search
Document Center

Edge Security Acceleration:Purge cache by hostname

Last Updated:Jun 22, 2026

Purge all cached resources matching specified hostnames. Multiple hostnames can be purged in a single operation.

Use cases

  • Purge all cached content across multiple hostnames of your site at once.

  • Clear all cached content for a specific hostname.

Procedure

  1. In the ESA console, select Websites. In the Website column, click the target site.

  2. In the navigation pane, choose Caching > Purge Cache.

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

    • Type: Select By Hostname.

    • 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:

      1. The ESA POP sends an origin request with the If-Modified-Since and If-None-Match request headers.

      2. The origin server compares the file modification time.

      3. 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.

      4. 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.

    • Purge Content: In the text box, enter the hostnames to purge. Separate multiple hostnames with a comma (,). Wildcards are not supported. For example:

      www.example.com,blog.example.com,shop.example.com

    image

  4. Click Submit.

  5. Monitor the purge status.

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

Availability by edition

Feature

Entrance

Pro

Premium

Enterprise

Daily quota

Not supported

100

1,000

2,000