Link11 WAAP
v5
v5
  • Link11 WAAP Documentation
  • Release Notes
  • Known Issues
  • User Guide
    • Introduction to Link11 WAAP
  • How Link11 WAAP Works
    • Traffic Filtering Process
    • Traffic Reporting and Analytics
    • Policy Mapping and Traffic Routing
    • Tagging
    • UI Overview and Common Elements
  • Console UI Walkthrough
    • Analytics
      • Dashboard
      • Events Log
    • Security
      • Global Filters
      • Flow Control Policies
      • Security Policies
      • Rate Limit Rules
      • ACL Profiles
      • Actions
      • Dynamic Rules
      • Quarantined
      • Content Filter
        • Content Filter Profiles
        • Content Filter Rules
    • Sites
      • Server Groups
      • Proxy Templates
      • Mobile Application Groups
      • Backend Services
      • Edge Functions
      • DNS Records
      • SSL
        • Load Balancers
        • Certificates
    • System
      • Interactive Challenge
      • SSO Configuration
      • Purge CDN Cache
      • Users Management
      • Security Alerts
      • Log Exporters
      • Version Control
      • System DB
      • Publish Changes
    • Account
  • Using the product
    • Best Practices
      • Saving and Publishing Your Changes
      • Enabling Passive Challenges
      • Understanding and Diagnosing Traffic Issues
    • How Do I...
      • Authenticate mobile app users
      • Ban, unban, and allowlist traffic sources
      • Bypass Link11 WAAP for loadtesting or other purposes
      • Configure a new path/section of a site
      • Control caching behavior
      • Enable GraphQL traffic
      • Enable mTLS (mutual TLS)
      • Protect sensitive information in logs and analytics
      • Quickly block an attacker
      • Redirect or block HTTP traffic
      • Run custom code
      • Set rate limits and exemptions
      • Stream event data to a SIEM solution or other destination
    • The Link11 WAAP API
      • Overview
      • Internal data structures
      • Using Swagger UI
      • Using curl
  • Reference Information
    • Acronyms
    • API
      • API access to traffic data
      • Types of namespaces
      • Namespace reference
        • ACL Profiles
        • Actions
        • Backend Services
        • Certificates
        • Configs
        • Content Filter Profiles
        • Content Filter Rules
        • Data queries
        • Dynamic Rules
        • Edge Functions
        • Flow Control Policies
        • Global Filters
        • Load Balancers
        • Log Exporters
        • Mobile Application Groups
        • Planets
        • Proxy Templates
        • Rate Limit Rules
        • Security Alerts
        • Security Policies
        • Server Groups
        • Tags
        • Tools
        • Users
    • Hostile Bot Detection / LWCSI
      • Environmental detection and browser verification
      • Client authentication
      • Biometric behavioral verification
    • HTTP Response Codes
    • Log Exporter Output
    • Pattern Matching Syntax
    • Query Filter Syntax and Best Practices
  • Support
Powered by GitBook
On this page
  • Prerequisites
  • Three-Step Purging Process
  • Step 1: Select the cache(s) to purge
  • To purge an entire planet
  • To purge one or more domains within the planet
  • Step 2: Initiate the purge
  • Step 3: (Optional) monitor the results

Was this helpful?

Export as PDF
  1. Console UI Walkthrough
  2. System

Purge CDN Cache

PreviousSSO ConfigurationNextUsers Management

Last updated 23 days ago

Was this helpful?

This feature allows admins to purge CDN caches at various scopes:

  • The entire planet

  • Specific domain(s) within the planet

  • Specific paths within domain(s)

A history of current and past activity is provided.

Prerequisites

This feature is available when at least one CDN has been set up in the system. (To do this, contact customer support.) If no CDN is currently configured, an error message will be shown.

Three-Step Purging Process

Purging requires these steps:

  1. Select the cache(s)

  2. Initiate the purge

  3. (Optional) monitor the results

Step 1: Select the cache(s) to purge

Cache selection is performed as follows.

To purge an entire planet

At the top left of the page, ensure that All domains in the planet is selected, then skip the remainder of Step 1, and continue to Step 2 below.

To purge one or more domains within the planet

At the top left of the page, ensure that Specific domains is selected. Additional controls will appear:

  • Select CDN: If there are multiple AWS load balancers, this control will appear. Select the AWS CDN provider for each domain/path where the cache has to be purged. In other situations (e.g., the planet uses the Google Cloud or Link11 CDN, or has only one AWS load balancer) this control is unnecessary and will not appear.

  • Alternative domain names: Specify a domain configured within the planet.

  • Add a specific path:

    • When this control is untoggled, caches for the entire domain will be purged.

    • When this control is toggled, the Path field will appear. Enter the path for which the cache should be purged.

Adding more domains/paths Multiple domains and/or paths can be specified for a purge.

After appropriate values have been entered into the controls described above, if another domain or path purge needs to be defined, select the New Host button and populate the new entry in the purge list. Repeat this process until all desired purges have been specified.

Step 2: Initiate the purge

Select the Purge CDN cache button. The specified purge(s) will appear in the Results list at the bottom of the page.

Step 3: (Optional) monitor the results

The Results list shows a history of purge commands submitted during the previous week. The list shows the date and time when each was submitted.

Within the list, the Status field shows the result of each purge during the most recent status update. Updates occur when the page is loaded or reloaded, and also each time the Refresh Status button is selected.

The possible statuses are:

  • In progress: as of the most recent status update, the purge was still being processed. (Note that depending on how recently the list was updated, the actual current status might be different.)

  • Done. The purge completed successfully.

  • Failed. The purge was attempted but was not successful. To try again, a new purge command must be submitted.

  • Not available. The purge was unsuccessful because the CDN was unavailable. To try again, a new purge command must be submitted.