sneaky TV style flash ads

[sidki3003]

This is a very interesting idea. I've played a bit with it, both, a local policy file and filtering crossdomain.xml.

Filtering because i was trying to block all "3rd party" flash objects. However, for each modification there was always a major site being broken.

(May. 10, 2009 01:42 PM)lnminente Wrote:  Someone know the good parameters in this file for doing this?

Below are those that were helpful for me. The URL in the comment goes into the details.

Local crossdomain.xml:

Code:

<?xml version="1.0"?>
<!DOCTYPE cross-domain-policy SYSTEM
  "http://www.adobe.com/xml/dtds/cross-domain-policy.dtd">
<!--
  Explained at:
  http://www.adobe.com/devnet/articles/crossdomain_policy_file_spec.html
-->

<cross-domain-policy>
<!--
  Domains from where *pulling* data is allowed.
  One tag per host, or "*" wildcard.  "foo" never matches.
-->
  <allow-access-from domain="foo" />

<!--
  Domains that are allowed to *push* data (via SOAP headers).
-->
  <allow-http-request-headers-from domain="foo" headers="*" />

<!--
  Meta policy.  "none" doesn't even allow this master policy file
  ("master-only" is default).
-->
  <site-control permitted-cross-domain-policies="master-only" />
</cross-domain-policy>

Anyway, when it came to simply redirect policy files from ad servers, using a local file which doesn't break XML - dummy.js in my case - did the job just as well, so i'm not going to use above file.

Regarding mentioned problem page, redirecting these files are removing the ads for me:
ad.doubleclick.net/crossdomain.xml
[^.]+.scanscout.com/crossdomain.xml