Auto Redirect www/non-www speeds up response time by caching redirect requests. Here’s how it works: The browser sends a request for www.example.com to QUIC.cloud CDN. QUIC.cloud sends the www.example.com request to your origin server. The origin server returns a response, indicating that the www.example.com request was redirected to example.com (the non-www domain). QUIC.cloud returns this … Read more
Yes. The crawler included in the LiteSpeed Cache for WordPress plugin will populate the cache at the origin server (but only if it is a LiteSpeed server), and also the cache at the QUIC.cloud PoP closest to the origin server. Under the current CDN cache policy, pages are stored at a PoP for 24 hours … Read more
Yes, however this should not be necessary under normal circumstances. The CDN cache is managed by the LiteSpeed Cache plugin for WordPress, and is sophisticated enough to know when content has changed and requires purging. That said, if you wish to purge the CDN cache manually, visit your QUIC.cloud Dashboard, and press the Purge All … Read more
By default, QUIC.cloud caches your site’s dynamically generated pages. This cache is controlled via the LiteSpeed Cache plugin for WordPress. QUIC.cloud can also cache your site’s static content. Be sure to set Static Cache to ON in your QUIC.cloud Dashboard‘s CDN Config area.
QUIC.cloud uses servers around the world to reduce the physical distance requests must travel. Additionally, QUIC.cloud can cache dynamic content at the CDN level, unlike other CDNs which must retrieve all dynamic requests from the origin server. CDN-level caching not only improves QUIC.cloud’s overall bandwidth speed, but it also minimizes the number of requests to … Read more
