Support

Find answers, guides, and tutorials to supercharge your content delivery.

Check If CDN Is Working

Learning how to check if your CDN is properly installed and working can save you time and reassure you that the integration process was successful. Doing so is a straightforward process and doesn't take much in terms of tools or time. This guide will…

CDN Error Codes

Error pages will not be cached, therefore only 200, 301, and 302 responses will be cached. KeyCDNs error pages show either a black or blue error code font color. All other error pages are coming from your origin server. 400 Bad Request In most of the…

CDN Troubleshooting Guide

This guide provides a list of troubleshooting suggestions for issues that you may experience when configuring a CDN. Troubleshooting tools KeyCDN Tools offers many tools, such as a DNS check (dig), HTTP header verification, and more. KeyCDN full…

Technical Questions

This section is focusing on technical questions on a deeper level and is the continuation of our FAQ. What cache statuses are there? Different cache statuses can occur for Push and Pull Zones. Here's an overview of possible cache statuses: HIT -…

KeyCDN Log Format

The log fields are separated by | (pipe). See the example below. Timestamp incl. msec (e.g. 1383918771.123) POP (point of presence) IP address of the client (e.g. 111.111.111.0 or 2001:be:ef::1) HTTP status code. A full list of all status codes is…

KeyCDN Log Forwarding

The raw logs can be received through syslog. Here's how to configure Log Forwarding syslog to receive your raw logs in real time: Log in to the KeyCDN dashboard. In the left navigation sidebar click Account and then Log Forwarding. Define the…

410 Gone Error - What Does It Mean and How to Fix It

What does a 410 Gone error mean? A 410 Gone error occurs when a user tries to access an asset which no longer exists on the requested server. In order for a request to return a 410 Gone status, the resource must also have no forwarding address and be…

Fixing 413 Request Entity Too Large Errors

The 413 Request Entity Too Large error already gives a hint in its name about what the solution to the problem could be. It's literally a size problem. This article will go through step-by-step how you can fix the 413 Request Entity Too Large error…

415 Unsupported Media Type

What does 415 Unsupported Media Type mean? A 415 Unsupported Media Type error occurs when the origin server refuses a particular request since the resource is in a format that is not supported by the server for the HTTP method used. This unsupported…

422 Unprocessable Entity Explained

What is 422 Unprocessable Entity? A 422 status code occurs when a request is well-formed, however, due to semantic errors it is unable to be processed. This HTTP status was introduced in RFC 4918 and is more specifically geared toward HTTP extensions…

KeyCDN uses cookies to make its website easier to use. Learn more about cookies.