Link11 WAAP
v2.18
v2.18
  • Link11 WAAP v2.18 Portal
  • Introduction
  • Getting Started
  • Setup Checklists
  • Marketplace Onboarding
    • AWS
      • Deploy Reblaze
      • Configure the Reblaze Platform
      • Set Up a Load Balancer for Traffic Routing
      • AWS Version Upgrade
    • GCP
      • Deploy Reblaze
      • Configure the Reblaze Platform
      • Set Up GCP Health Checks
      • Set Up GCP Load Balancer
      • GCP BYOL Upgrade
  • Console UI Walkthrough
    • General UI flow
    • Traffic
      • Traffic Concepts
      • Dashboard
      • View Log
    • Security
      • Security Section Concepts
      • Dynamic Rules
      • Quarantined
      • Profiles
        • Profile Concepts
        • Profiles
        • ACL Policies
        • WAF/IPS Policies
        • Custom Signature
      • Args Analysis
      • Tag Rules
      • Rate Limiting
      • Cloud Functions
    • Settings
      • Web Proxy
      • Backend Services
      • Error Pages
      • SSL
      • DNS
      • CDN
      • Planet Overview
      • Global
      • Account
  • Using the product
    • Best Practices
      • Saving and Publishing Your Changes
      • Enabling Passive Challenges
      • Using the Reblaze Query Box
      • Understanding and Diagnosing Traffic Issues
    • How Do I...
      • Ban, Unban, and Whitelist Traffic Sources
      • Bypass Rate Limits for Loadtesting
      • Control Caching Behavior
      • Filter by Content
      • Quickly Block an Attacker
      • Secure Traffic from a Third-Party Page
      • Set Rate Limits and Exemptions
      • Set up SIEM/SOC integration
      • Video Tutorials
        • DNS Training
    • API
      • Reblaze REST API
      • Mobile SDK
  • Reference Information
    • Access log-structure
    • Acronyms
    • Deployment Terminology
    • Hostile Bot Detection / RCSI
      • Environmental detection and browser verification
      • Client authentication
      • Biometric behavioral verification
    • HTTP Response Codes
    • Pattern Matching Syntax
    • Signatures
    • Tags
    • TTL Expression Syntax
  • Support
Powered by GitBook
On this page
  • Initial configuration
  • Defining the caches to purge
  • Selecting the CDN to purge
  • Purging the cache(s)

Was this helpful?

Export as PDF
  1. Console UI Walkthrough
  2. Settings

CDN

Purging of caches

PreviousDNSNextPlanet Overview

Last updated 3 years ago

Was this helpful?

Sometimes it is beneficial to purge a Content Delivery Network (CDN) cache. Reblaze provides this ability on this page.

You can purge a single cache or multiple caches, across one CDN or multiple CDNs simultaneously. Both AWS and GCP CDNs are supported.

Initial configuration

Once initial configuration is complete, purging becomes available on this page.

Defining the caches to purge

The top part of the window shows a list of caches to purge.

To add an entry:

  • Select the + button.

  • In the Path field, enter a relative path (such as /*) or a fixed path (such as /static/image.png). If you leave this field empty, all caches will be purged.

  • Select the add button at the end of the entry.

When the cache list has at least one item, the Purge button becomes available.

Selecting the CDN to purge

When there is more one CDN provider configured, by default Reblaze will purge all of them.

If instead you wish to select a certain CDN provider, check the Select CDN manually checkbox. A dropdown list will appear where you can select the provider.

Purging the cache(s)

Selecting the Purge button will send purge commands to the selected provider(s). The cache list will be moved to the PURGE STATUS list at the bottom of the window, and the status for each purge will be shown.

The completion time will vary by the provider. To update the statuses in the list, select the Refresh control at the top right of the list.

Once you have launched a purge, you can exit this page. The purge(s) will run in the background; you do not need to wait here for them to complete.

The entries in the status list will be retained for one week.

Initial configuration of the CDN provider(s) within your planet is done by Reblaze personnel. Please for assistance with this.

In the Host field, enter the domain. If you leave this field empty, all hosts (i.e., all sites/applications shown in the ) will be purged.

contact support
Planet Overview