What is the Origin used for?
The Origin field lets StackPath know the destination of the host where we should be pulling assets from. There are two basic ways in which this host can be specified:
You can enter the IP of the host server
You can en...
Read More »
The purpose of a canonical header tag is to tell search engines that a given URL is the authoritative source for a piece of content, eliminating the damage to SEO rankings if there are multiple versions of the same piece of content. StackPath now ...
Read More »
CDN Settings: HTTP/2 Server Push
What does it do?
HTTP/2 Server push allows you to push assets to the client or browser (User) in advance (before the user requests these assets) and by doing so, reduce latency.
When enabled, the CDN will look for the HTTP/2 server push header (us...
Read More »
EdgeRules for Common Use-Cases
EdgeRules are versatile and customizable, but it can be a daunting task at times to curate a specific rule that is tailored to the desired outcome. Provided here are examples of EdgeRules that are commonly applied to solve a variety of everyday us...
Read More »
Getting Started with Custom EdgeRules
EdgeRules provide users a great amount of flexibility to customize the behavior of the StackPath CDN. EdgeRules perform the specified action upon requests that match user-defined triggers.
StackPath's custom rules engine provides additional contr...
Read More »
StackPath can validate the origin server's SSL certificate when pulling content. A valid SSL certificate is both:
Issued by a known and trusted certificate authority. Self-signed certificates are not trusted.
Not expired.
StackPath aborts the co...
Read More »
What does it do?
Much like HTTP, WebSocket is a communications protocol between a web browser and an origin server that operates on standard ports TCP 80 and 443. Instead of a series of connections, WebSockets establish a single long-held bi-direc...
Read More »
What does it do?
The pull protocol controls the protocol that the StackPath CDN uses to pull content from your origin server.
When and how should I use it?
Choose one of these options:
HTTP or HTTPS: StackPath uses the same protocol that site vis...
Read More »
Settings: Origin Authentication
What does it do?
Basic HTTP authentication is a method to protect sensitive web content behind a simple username and password prompt.
When configured, StackPath's CDN uses your username and password when requesting content from your origin server....
Read More »
What is the Host Header?
Many web servers are configured to serve content for multiple sites from the same IP address. The host header tells the web server which site to load content from. It's sent as part of the HTTP request, for example:
GET / ...
Read More »
What does it do?
Backup servers provide an extra layer of redundancy to ensure that your site continues running when your primary origin is unavailable. StackPath's CDN loads content from the backup origin if the primary origin is unavailable.
Def...
Read More »
What does it do?
The origin address is the location from where StackPath's CDN pulls content from. There are two ways to enter your origin's address:
By IP address: StackPath loads content from your origin directly by IP. Consider setting a Host ...
Read More »
What does it do?
HTTP/2 optimizes the flow of content between clients and servers. It’s fully backwards-compatible with HTTP/1.1, so websites will work the same with either protocol.
When a user connects to a server, their browser negotiates an HT...
Read More »
CDN Settings: CORS Header Support
What does it do?
A cross origin request is a request for a resource that exists on a different origin from the requesting one. For instance, when a.example.com requests the webfonts.eot asset from b.example.com ( https://b.example.com/webfonts.eot...
Read More »
CDN Settings: Browser cache TTL
What does it do?
Modern web browsers have a local cache that is used to save and deliver resources instead of requesting them from a website. Serving content from the local browser cache is always a faster experience than requesting content from a...
Read More »
What does it do?
When a user requests an asset such as an image, CSS file, or HTML document, the request goes through the StackPath CDN edge network. If the StackPath CDN server already has the asset, it is served from cache instead of requesting ...
Read More »
CDN Settings: Content Persistence
What does it do?
Assets such as an image, CSS file, or JS file are saved with an expiration time, or lifetime, when they are saved on the CDN's cache. After the lifetime expires, the CDN fetches the asset again from the origin server the next time...
Read More »
CDN Settings: GZIP Compression
What does it do?
GZIP is a popular and effective compression method that reduces response sizes by 60-70%, vastly lowering response times and improving site performance.
Enabling GZIP compression is a standard practice to provide smaller file siz...
Read More »
CDN Settings: Dynamic caching by header
What does it do?
When a user requests an asset such as an image, CSS file, or HTML document, the request goes through the StackPath CDN edge network. If the StackPath CDN server already has the asset, it is served from cache instead of requesting ...
Read More »
CDN Settings: Query string control
What does it do?
A query string is the part of a URL that comes after a question mark and assigns values to specified parameters.
The correct query string caching behavior results in a better cache hit ratio, which improves site performance.
When ...
Read More »
95% of questions can be answered using the search tool. This is the quickest way to get a response.