I have an app that fetches config json from a server I control. That server has a crossdomain.xml file at the root. Back in October, I was able to build my app for webplayer and it worked just fine–on Windows and Mac, on Chrome, Firefox, Safari and IE. That same old build continues to work fine.
When I build it again using 4.3.3f1, the resulting file no longer works on Chrome and Firefox: It says “Rejected because no crossdomain.xml policy file was found”. This happens on both Windows and Mac. The app continues to work fine in Safari and IE, however (on both Windows and Mac).
Since I own the server I’m connecting to, I can review its logs, and the logs show no actual attempt to fetch crossdomain.xml–as far as I can see, the player isn’t even trying to get the crossdomain file. However, for the sake of completeness, here’s the file it would receive if it requested the file, which it doesn’t:
<?xml version="1.0"?>This file is served with a mimetype of “text/x-cross-domain-policy”.
So: Why are Chrome and Firefox different from Safari and IE, why did this difference come into existence in the past few months, and most importantly, what can I do to get around it?