HTTP header from %s specifies meta-policy 'by-ftp-filename', which is only applicable to FTP, not
HTTP.
A by-ftp-filename meta-policy was found in an X-Permitted-Cross-Domain-Policies HTTP response
header, but it is only valid for FTP servers.
The X-Permitted-Cross-Domain-Policies header has been ignored, but any policy file at this URL has not
necessarily been ignored (there should be a further error message if it is).
Conflicting meta-policy in HTTP header from %s %s
Multiple conflicting meta-policies were found in one or more X-Permitted-Cross-Domain-Policies HTTP
header.
The entire meta-policy string is shown, as received from the server. If multiple
X-Permitted-Cross-Domain-Policies headers were provided, they have been coalesced into a single
header with semicolon-separated values as is normal for HTTP headers. The client applied the most
restrictive meta-policy that was found in this string. It is generally not legal to provide multiple
meta-policies in HTTP response headers; the only exception is none-this-response, which may be
combined with any other meta-policy, but only affects the individual HTTP response where it is found.
Meta-policy %s in HTTP header from %s conflicts with previously established meta-policy %s
Meta-policies are incorrectly configured. It is likely that a less restrictive meta-policy was found in the
HTTP header before a more restrictive policy. The less restrictive meta-policy may have been in effect for
some time until the conflict was found later.
Ignoring <site-control> tag in policy file from %s. This tag is only allowed in master policy files.
A meta policy was specified in a non master policy file. The
site-control
tag is only legal in master policy
files (/crossdomain.xml on an HTTP/HTTPS/FTP server, or a socket policy file from port 843).
The meta policy has been ignored, but the policy file has not necessarily been ignored (there should be a
further error message if it is).
Ignoring <site-control> tag in policy file from %s. The 'by-content-type' meta-policy is only
applicable to HTTP sites.
A
by-content-type
meta policy was incorrectly specified in the policy for an FTP server since it is only valid
for HTTP and HTTPS servers.
The meta policy has been ignored, but the policy file has not necessarily been ignored (there should be a
further error message if it is).
Ignoring <site-control> tag in policy file from %s. The 'by-ftp-filename' meta-policy is only
applicable to FTP sites.
A
by-ftp-filename
meta policy was incorrectly specified in the policy for an HTTP(S) server.
The X-Permitted-Cross-Domain-Policies header has been ignored, but the policy file has not necessarily
been ignored (there should be a further error message if it is).
Ignoring <site-control> tag in policy file from %s. The 'none-this-response' meta-policy is only
allowed in the X-Permitted-Cross-Domain-Policies HTTP response header.
A none-this-response meta-policy was incorrectly specified. It is only valid in the
X-Permitted-Cross-Domain-Policies HTTP response header and is intended as a mechanism by which
HTTP servers can prevent server scripts from generating policy files.
The meta-policy has been ignored, but the policy file itself has not necessarily been ignored (there should
be a further error message if it is).
Unrecognized meta-policy in policy file from %s %s
An invalid meta-policy was specified in the master policy file.
Section 7 Cross Domain Configuration
Application Security Guide
Page 72
Section 7 Cross Domain Configuration
