There are many ways to customize your content delivery. From instantaneous cache purge to query string control, you can customize TTLs and more to configure the delivery of your content across the CDN for a fully optimized experience.
How to access CDN Configuration Settings
- Log into the StackPath Portal
- Select CDN from the left-side navigation
- Select edit next to the site you would like to update
- Select Settings in CDN site menu
If you're not using StackPath as a DNS provider you'll need to either set the DNS records for your delivery domains as CNAME types with this value or input this value into your CMS caching plugin. This target supports both HTTP and HTTPS delivery.
Delete your content from the cache so that StackPath will retrieve it from the origin on next request. You can purge everything in your site, or you can choose to selectively purge by full URL or recursive path
Browser Cache TTL
Set the length of time that client browsers use to locally cache your content, or defer to the value passed by your origin
The protocol, domain, and path that we will use to retrieve content from your origin
Enable this to reduce the file size of your text-type content, which will improve delivery speeds. You can select a level from 1 (least compressed) to 9 (most compressed) if you're concerned about the CPU impact of decompression for your end users.
CDN/Edge Cache TTL
Set the maximum length of time that the CDN will cache your content before going back to the origin, or defer to the value passed by your origin
Enable this to keep content in cache beyond its expiration time in case we can't reach your origin. We'll check the origin, and if the file is there we'll update it. If not we'll serve the expired asset from cache.
CORS Header Support
Cross-Origin Resource Sharing (CORS) is a mechanism to allow for browsers to use content and code from multiple domains. If you disable this then client browsers will only be able to process scripts from the delivery domain they're connected to. If you enable it, we will send an "Access-Control-Allow-Origin: *" header to the client browser to let it know your site may need to leverage external scripts.
HTTP/2 is the next generation of web protocol. It has features like binary encoding and multiplexing that make web connections faster and more efficient if your site is designed to make use of them.
Please note that StackPath HTTP/2 support does not include Push, and is only used on the connection between the client and the edge. Using HTTP/2 to the origin would in most cases have small to nonexistent performance benefits.
Query String Control
Determine how you want StackPath to treat URLs that have a query string portion (a "?" followed by a series of keyword/value pairs represented by "&x=y". Ignoring the query string means we will cache https://example.com/file.txt?ver=1 and https://example.com/file.txt?ver=2 identically based on which is requested first. "Standard" behavior is that we will cache these 2 URLs distinctly
If you know that a large portion of your customer base is on IPv6 networks you can use this feature to add an AAAA (IPv6) record to the DNS response for your domain. If you're not certain, please be aware that there can be negative performance impacts in regions and on devices where IPv6 support is not yet fully available.
This is the list of domains for which StackPath will use this site configuration to respond to requests. Add a delivery domain for every domain you wish to use this configuration.