It may be that although you have the same host and protocol between the client page and server, the different port causes Flash to fail the same-origin test and request the crossdomain. Xml to see what it's allowed to do. I'm assuming the page hosting your Flash content is running on port 80?
If that's the case, check out Wikipedia's article on the same origin policy (en.wikipedia.org/wiki/Same_origin_policy) for the details The crossdomain. Xml doesn't seem to be too cumbersome for local testing and is pretty well documented on help.adobe.com. You can create a crossdomain.
Xml in the root of your website like this, which will allow all access:? Xml version="1.0"?
It may be that although you have the same host and protocol between the client page and server, the different port causes Flash to fail the same-origin test and request the crossdomain. Xml to see what it's allowed to do. I'm assuming the page hosting your Flash content is running on port 80?
If that's the case, check out Wikipedia's article on the same origin policy (en.wikipedia.org/wiki/Same_origin_policy) for the details. The crossdomain. Xml doesn't seem to be too cumbersome for local testing and is pretty well documented on help.adobe.com.
You can create a crossdomain. Xml in the root of your website like this, which will allow all access: I wouldn't use the above for anything other than local development as you're basically allowing any domain to request content. Hope this helps!
Thanks! I'll need to look into how Flash does it's same-origin testing. To be more specific, my "server" is an xmlrpc server that uses HTTP for transport.It does not handle GET requests at the moment, although I could certainly force it to.
The source of the flash content is a local file generated by the IDE I'm using at the moment (Amethyst plugin for Visual Studio). – Russ Jun 3 at 3:23 Rolling your own xmlrpc server sounds like fun, although you do have to support any additional nuances Flash throws at you... like the GET for crossdomain.xml. I'm not sure of your implementation, but it might be worth it to look into leveraging an existing web stack and then building out a simple web service instead of using xmlrpc.
If you're using C#/MS stack, check out WCF REST with plain old xml - see: link – mrdc Jun 3 at 4:19 1 +1. Mrdc is right. The domain and port needs to be the same to ignore crossdomain policies.
If the port is different than the webservers, then it'll look for crossdomain.xml. Easiest way to get this working if to have your server in an application container (like glassfish or tomcat if using Java/. Net) or use whichever web server to serve up server side scripting language (php, asp, etc).
Much easier to all have it done with just one server. – J_A_X Jun 3 at 13:35 I'm not sure what to make of it, but when I switched it to use a standalone flash player versus loading up the flash via html in a browser, the crossdomain issue goes away completely.Ie: it is working fine now (and now that this has happened I expect that this is how I ran it successfully in the past as well). I'm not sure if this matches the ports-must-match theory... does it?
– Russ Jun 3 at 16:45 1 Using Flash player (fp) avoids the crossdomain issue as fp doesn't have a hosted context. When Flash is hosted on a web page, the request goes something like: User -> Webpage (localhost:someport) -> Web Service (localhost:someotherport) and fails the same origin test between the Webpage and Web Service. When using fp you only have User w/Flash player (no hosted context) -> Web Service The web service is the only hosted context that the same origin is tested against.
And, since there's only one context, it doesn't check for cross domain issues. Hope this helps! – mrdc Jun 3 at 19:08.
Using the policyfile. Txt I figured out that the policy file was denied because there was no Content-Type specified by the server. This explains why it was impossible to find anything blogged about it.
Hope this helps someone. In Flex 4. 5 Mac /Users/YOUR_USER_NAME/Library/Preferences/Macromedia/Flash Player/Logs>tail -f policyfiles.txt.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.