
Originally Posted by
scottstamp851
Nice tutorial, Wesley. It should be noted though for clarification, this "error" is actually a warning. It won't prevent the crossdomain file from being loaded, Chrome just doesn't like it. It's considered a potential security issue. That being said, it's not really a big deal if someone sends a modified crossdomain.xml file using a proxy to your client. They're the only ones that get that content, and they can't really do anything with it.
Useful explanation of editing the code, but not really something people need to do for their hotels unless they're particularly picky.