Getting Started

Deployment Deployment - Diagnose Migrations Staging

Site Management

Backups Client Reporting Passwords Plugin Automation Plugin Management - Global Plugins & Themes - Diagnose Plugins & Themes - General Plugins & Themes - Git Plugins & Themes - Logs Must Install White Label WordPress Updates

Caching & Performance

Caching Caching - Blogs/Articles Caching - Diagnose Caching - Git Caching - WooCommerce Redis Optimize & Scale

Security

Security Security - Firewall

SMTP, CDN & DNS

SMTP SendGrid CDN CDN - AWS CDN - Cloudflare CDN - Diagnose Domains & DNS

Server & Tools

Analytics & Logs CRON Jobs Database Debug Tool Git Monitoring PHP Settings Redirects SEO Tools Server Errors sFTP SSL

Staq Billing

Staq Billing > Account Staq Billing > Client Staq Billing > Setup

Media

Media Media - Diagnose Media - Optimize

Accounts & Billing

Accounts & Billing

General

WordPress Hosting Website Diagnose Troubleshoot - Other

Exclude Paths from Next-Gen CDN Cache


On this page

    Understanding Cache Control in WordPress

    WordPress doesn’t send “No-Cache” headers by default.

    At Staq, we maintain this flexibility by not enforcing “No-Cache” headers when our Page Cache feature is off, ensuring compatibility with various caching plugins.

    Next-Gen CDN Use Cases

    The Next-Gen CDN is optimized for delivering static content quickly to users globally. It’s ideal with a caching plugin but can also support dynamic content in certain scenarios.

    Excluding Paths from CDN Caching

    To exclude specific paths from Next-Gen CDN caching:

    1. Navigate to the Staq dashboard, under Settings > WP Config File.
    2. Add the WPSH_CLOUDFRONT_EXCLUDE_PATHS constant, listing paths to exclude in a comma-separated format:
    "/path1,/path2"

    For example, excluding the homepage and shop:

    "/,/shop"

    Need some help?

    We all do sometimes. Please reach out to our support team by dropping us a support ticket. We will respond fast.