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).
Meta-policy %s in policy file 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
policy file before a more restrictive policy. The less restrictive meta-policy may have been in effect for
some time until the conflict was found later.
Domain %s does not specify a meta-policy. All policy files from this domain will be ignored.
This common message appears when the client obtains a policy file from an HTTP, HTTPS, or FTP server
that has not specified a meta-policy.
Domain %s does not specify a meta-policy. Applying default meta-policy 'all'. This configuration is
deprecated.
This common message appears when the client obtains a policy file from an HTTP, HTTPS, or FTP server
that has not specified a meta-policy.
Domain %s does not explicitly specify a meta-policy, but Content-Type of policy file %s is
'text/x-cross-domain-policy'. Applying meta-policy 'by-content-type'.
The client looked for a meta policy in the HTTP headers and in the master policy file, but did not find it. A
policy file was returned with a Content-Type of text/x-cross-domain-policy, which indicates that the
administrator deliberately made changes to support meta-policies.
Since the official Content-Type for HTTP policy files is in use, the client assumes a meta-policy of
by-content-type for this domain. It is recommended that, for clarity, this server should explicitly declare a
meta-policy, rather than relying on this implicit mechanism. This can be done using a <site-control> tag in
the master policy file, or using the HTTP response header X-Permitted-Cross-Domain-Policies.
Ignoring policy file at %s due to meta-policy '%s'.
A meta-policy found in a
site-control
in the master policy file or in an X-Permitted-Cross-Domain-Policies
HTTP header expressly forbids this file from being valid as a policy file, so this policy file will not authorize
any operations.
If you intended for this policy file to be valid, change its Content-Type or its FTP filename or change the
meta-policy.
Policy file at %s invalidates its own <allow-access-from> directives by declaring the meta-policy
'none'.
The policy file specifies a meta-policy of
none
as well as
allow-access-from
. Remove
allow-access-from
.
The declared meta-policy
none
means that no policy files are permitted on this server and that the master
policy file is permitted to exist only to declare the meta-policy and cannot contain
allow-access-from
.
7.6.4 Policy file parsing/syntax errors
[strict] Ignoring policy file with incorrect syntax %s
The policy file syntax is incorrect. Refer to the
Cross Domain Policy File Specification
.
Ignoring invalid <allow-access-from> tag for domain '%s' in policy file at %s
The string identifying the domain was not recognized as valid. This particular <allow-access-from>
directive will be ignored, although other directives in the same policy file may be valid and accepted.
Ignoring illegal port number specification '%s' in policy file at %s
The
to-ports
attribute in
allow-access-from
was not recognized as a valid port range.
Application Security Guide
Section 7 Cross Domain Configuration
Section 7 Cross Domain Configuration
Page 73
