LogoLogo
  • Home
  • Game Hosting
    • Get started
      • Set Up Guide
      • Game Template
      • Game Deploy
    • Overview
      • API guide for game hosting
      • Terminology
      • API v3 usage
      • API v3 authentication
      • API v3 error handling
      • API v3 error codes
    • Processes
      • Application Management
      • Application Build Provisioning
      • Application Build Management
      • Deployment Configuration
      • Deployment Process
      • Automatic Deployment
      • Automatic Scaling
      • Dependency Installation
      • Patching
        • Utility patching
        • Forced Deployment
        • Forced Deployment Manually
        • Rolling Deployment
        • Rolling Deployment Manually
        • A/B Deployment
        • A/B Deployment Manually
    • Elements
      • Application
        • Applicationproperty
        • Applicationbuild
        • Applicationbuildproperty
        • Applicationbuildconfiguration
        • Applicationinstance
        • Applicationinstanceproperty
        • Applicationinstanceip
        • Label
        • Metadata
        • Element Relations
        • Platform Variables
      • Deployment
        • Fleet
        • Deploymentprofile
        • Deploymentregion
        • Deploymentcontainer
        • Deploymentcontainerlocation
        • Deployment Templates
          • Gamedeploymenttemplate
          • Utilitydeploymenttemplate
          • Dependencydeploymenttemplate
        • Host Capacity
          • Instancetypecapacity
        • Dclocation
      • Host
        • Hostcpu
        • Hostip
        • Hostdisk
        • Hostmemory
      • Patching
        • Patchjobapplicationbuild
        • Patchjobfleet
        • Patchjoboverallprogress
        • Patchjobemail
    • Features
      • Task System
      • Platform Events
    • Cloud Usage
      • Cloud Credentials
      • Cloud Instance Types
    • Game Integration
      • Orchestrator overview
      • Matchmaker Allocation
      • Ping beacons overview
      • Upgrade GCP VMs to AMD Milan or later
      • Game server run status
      • Gameliftanywhere integration
      • Game Hosting-SDK
        • Build
        • Integration Guide
        • Sdk Unity Plugin
        • Sdk Unreal Plugin
      • Management Protocol
        • A2S
        • Arcus
          • Usage
          • Configuration
          • Packet Structure
          • Handling Server Query Response
          • Available Opcodes
        • Arcus V2
          • Request Response
    • Events
    • Examples
      • Registering Application And Builds
      • Env From Scratch
  • Anti-DDoS
    • About Anti-DDoS
    • DDoS attack types
    • Anti-DDoS onboarding guide
    • DDoS category attack types
  • Compute
    • Dedicated Bare Metal
      • Catalog
    • FlexMetal
      • Getting started with FlexMetal
      • OS Customization
      • Talos installation
      • Tag management
      • Troubleshooting
      • Check your quota usage
  • Contact
  • Api
    • General
    • Game
    • GLAD API
  • Endpoints
Powered by GitBook
On this page
  • Purge using the CDN front end
  • Purge using the CDN API
  • Related topics
  1. CDN

CDN actions: How to purge

Last updated 2 months ago

Below you can read how to remove cached content from the CDN's edge servers. You can either choose to remove cached content though the CDN front end, or using the CDN API.

Purge using the CDN front end

  1. Log into the CDN control panel: Open a web browser and navigate to the control panel URL. Enter your login credentials to access the control panel dashboard.

  2. Access Cache Management: Once you have logged in, select the Cache tab.

  3. Specify content to purge: In the Purge selected URLs field, enter the URLs you want to purge. Be sure to add each URL in a new line. Alternatively you can click Start purging all to purge all of your cache.

  4. Confirm and initiate purge: Review your list of files/URLs you entered to confirm what you want to purge. Click Start purging to start the process.

  5. Action verification: Once the purging is complete, you can verify its success by accessing the purged files/URLs. These files/URLs should now be fetched from the origin server, which indicates the purging was successful.

Purge using the CDN API

  1. Open API: Obtain API credentials (such as API keys or tokens). These credentials will authenticate your API requests.

  2. Identify content to purge: Determine the content that you want to purge. This could be a specific URL, a group of URLs, a file path, or a wildcard pattern that matches the content that you want to remove.

  3. Construct the API request: Create an HTTP request to the appropriate API endpoint.

  4. Send an API request: Use the HTTP method specified in the CDN's . Include the necessary headers, API credentials, and contact identifiers in the request payload.

  5. Process the API response: The API call will return a response indicating the status of your request. Check the response for success or error messages.

Related topics

API Swagger documentation
About CDN
How to pre-warm