.Swf Flash files are quite common to use. Request posted by BlazingCDN as part of your website may not work correctly. This is due to how Flash files work, which verifies from which domain Flash files and other media are loaded. To do this, you must set a cross-domain join policy. It is on your side to create a crossdomain.xml file in the Origin domain, the origin of the CDN service. Sample code below:
<?xml version=”1.0″?>
<!DOCTYPE cross-domain-policy SYSTEM “http://www.domain.com/xml/dtds/cross-domain-policy.dtd”>
<cross-domain-policy>
<allow-access-from domain=”*”/></cross-domain-policy>
See also:
Using HTTP/2 w BlazingCDN
Setting up BlazingCDN for SEO
Setting a Cache in BlazingCDN
Restricting access to BlazingCDN origin server
Origin Protocol in BlazingCDN
Origin Port in BlazingCDN
Manage content in the BlazingCDN cache
How to accelerate website with BlazingCDN
Cookies in BlazingCDN
BlizngCDN Origin protection
BlazingCDN with a SSL
BlazingCDN URL Signing
BlazingCDN Static service
BlazingCDN Service Domains
BlazingCDN recommended Gzip compression
BlazingCDN Password
BlazingCDN Origin Domains Setup
BlazingCDN Hotlinking Policy
BlazingCDN Flash files – cross-domain cases
BlazingCDN and IP Access Policy
BlazingCDN and Cloudflare
BlazingCDN and Amazon S3
BlazingCDN Access Policy
BlaizngCDN server limits