<?xml version="1.0"?>
<!DOCTYPE cross-domain-policy SYSTEM
"http://www.adobe.com/xml/dtds/cross-domain-policy.dtd">
<cross-domain-policy>
<site-control
permitted-cross-domain-policies="none"
/>
</cross-domain-policy>
The following is the most permissive master policy file definition (
strongly not recommended
). It allows
any policy file on the target domain to grant permissions, allows access to any of its file, and permits any
header to be sent to the server. All of this possible even through HTTPS despite the source being HTTP:
cross-domain-policy: Least restrictive policy
<?xml version="1.0"?>
<!DOCTYPE cross-domain-policy SYSTEM
"http://www.adobe.com/xml/dtds/cross-domain-policy.dtd">
<cross-domain-policy>
<site-control
permitted-cross-domain-policies="all"
/>
<allow-access-from
domain="*"
secure="false"
/>
<allow-http-request-headers-from
domain="*"
headers="*"
secure="false"
/>
</cross-domain-policy>
7.2.5 Meta vs. master policies
While
Meta policy: Allowing non-master policy files
does not allow data access to this
target domain, it does define a meta-policy that allows other policy files within this domain to determine
how access is handled. In this case, the client is instructed to look for a policy file other than the master for
permissions related to this domain.
Meta policy: Allowing non-master policy files
<?xml version="1.0"?>
<!DOCTYPE cross-domain-policy SYSTEM
"http://www.adobe.com/xml/dtds/cross-domain-policy.dtd">
<cross-domain-policy>
<site-control
permitted-cross-domain-policies="by-content-type"
/>
</cross-domain-policy>
Meta policy: allowing only a master policy
defines a meta-policy that allows only this
master policy file to function for this target domain. It allows access to data on example.com and all of its
subdomains:
Meta policy: allowing only a master policy
<?xml version="1.0"?>
<!DOCTYPE cross-domain-policy SYSTEM
"http://www.adobe.com/xml/dtds/cross-domain-policy.dtd">
<cross-domain-policy>
<site-control
permitted-cross-domain-policies="master-only"
/>
<allow-access-from
domain="*.example.com"
/>
</cross-domain-policy>
7.2.6 HTTP-HTTPS communications
Section 7 Cross Domain Configuration
Application Security Guide
Page 58
Section 7 Cross Domain Configuration