Debugging is the process that is systematically reducing the number of errors. Let’s see what you can do when trying to implement this process with BlazingCDN.
To carry out the process, you need:
- Service domain – XXX
- Service identifier – ZZZ
The service identifier is a CDN ready domain. Please note that DNS configuration changes can take 48 hours to propagate. We do this by adding a CNAME record. Static content must be accessible via HTTP or HTTPS. When creating a new CDN service, it can take a few minutes to distribute it to all CDN locations, so don’t worry if your CDN service doesn’t show up immediately. If you cannot find the given URL resource, it is worth using curl (code return 200). There you will receive information about the protocol, date, server, and last modification. Status code 200 missing; fix it on the origin server. You may need to clear the CDN content after changing the settings in the source.
Raw access logs
Overview of BazingCDN services
Origin and BlazingCDN content – differences
HTTP/2 tools and FAQ at BlazingCDN
CDN usage reports
BlazingCDN and Two Factor Authentication
BlazingCDN advanced reports