Does the cross-domain.xml at the webservice server provide access to the domain you are publishing the SWF to?
With .NET one generally needs a crossdomain.xml in the application root. If the webservice (wsdl) is in a subdirectory and it has it's own web.config it will generally need a crossdomain.xml file in the same directory as the webservice.
I use the term "generally" because server configurations vary, for my servers, I always need a crossdomain.xml file for any directory I want to expose a webservice from. For example if I have a webservice in a directory named stocks and the url is http://www.mysite.com/stocks/mywsdl.asmx I need a crossdomain.xml file in the stocks directory. Not the server root directory / for http://www.mysite.com
Many make the mistake with .NET and place the crossdomain or clientaccesspolicy files in the server root and think it will cover all webservices globally. In most cases it causes access violations.
The image below is of a live service in a sub directory svr. This is the structure I have to use when exposing webservices from .NET
Hi, and thanks for the responses. Unfortunately I am still not able to get this working! I have now given up on the proxy solution, and have asked my partner company to put the following crossdomain.xml on their server:
<allow-access-from domain="*" headers="*" secure="false"/>
The application still gives me the same Security Error response. I am using charles for debugging. I've observed that the crossdomain.xml file is not loaded from their server unless i put loadPolicyFile("http://pathTo/crossdomain.xml"); in my code, and I'm still not sure if thats the best practice, or if the file should just be loaded automatically.
The crossdomain.xml file is in the directory where the SOAP service is being served from.
I'm still trying to solve this problem, and appreciate the help, and any further ideas i could try.
thanks in advance