CDN caches content in the new origin domain for static video and live research assets, as well as Origin Storage for the same assets. The process takes place on the BlazingCDN network and allows content to be delivered quickly.
Origin of resources and their publication
Your static and video resources on BlazingCDN may be needed by sharing via sharing from your server or hosting a storage source. For Live resources, you can stream them via URL or via PoP Origin streaming server. (push publications).
Service domain and service ID
Service Domain – This is the service name/label in BlazingCDN and defines a custom variant. The service domain (given during the creation of the CDN service, editable) and the service ID (assigned top-down) are opposites of the CDN to Origin – both define where (through which domain) you can access the CDN content and must be unique.
Raw access logs
Overview of BazingCDN services
HTTP/2 tools and FAQ at BlazingCDN
Debugging a BlazingCDN service
CDN usage reports
BlazingCDN and Two Factor Authentication
BlazingCDN advanced reports