A crossdomain.xml file resides on each remote server that is expected to be contacted from a SWF hosted on another server.
For example, you could place a crossdomain.xml file on http://www.abc.com/crossdomain.xml and in there allow 192.168.10.160 loaded SWFs (i.e. Flex apps) to contact it. -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Mike Anderson Sent: Wednesday, June 08, 2005 6:09 PM To: [email protected] Subject: [flexcoders] CrossDomain.xml file question Hello, I am continuing this from the whitelist thread... Could you all clarify for me, precisely *where*, and in how many places, I must locate the "crossdomain.xml" file? Lets say, my Flex Server page resides at "http://192.168.10.160/mypage.mxml";, and I am trying to access a Remoting Service which resides at "http://www.abc.com";? It's obvious which entries need to be made in the actual .xml file, but WHERE must I place the actual files? My Remoting server is actually a Microsoft IIS Server, using the .NET Flash Remoting .dll file. For those .NET remoting users out there, in order to properly setup Flash Remoting for .NET, you must first setup a Virtual Directory, and then have a /bin directory underneath that (containing the .dll file). My actual remoting calls are made to "http://www.abc.com/virtualDirectory/flashgateway.aspx so the question is, where do I actually place the crossdomain.xml files? Do I have to place one in the actual Flex Root directory? If so, would it be the Web Root, or the directory in which the .MXML file is being served from? Also, the same goes for my IIS Web Directory - do I place it in my Virtual Root? Any other places that I should be concerned with? If you could all clarify that for me, I'd be very appreciative. Thanks, Mike Yahoo! Groups Links Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/flexcoders/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
