I can see the xml but I am not sure what needs to be updated there in order
to avoid this error. 


Tracy Spratt wrote:
> 
> "crossdomain.xml file which is in the same folder as my project".  It
> should be at the root of the web server, so that you can do,
> http://www.mydomain.com/crossdomain.xml, and see the xml.
> 
> Tracy  
> 
>  
> 
> ________________________________
> 
> From: [email protected] [mailto:[EMAIL PROTECTED] On
> Behalf Of moj2joj
> Sent: Friday, November 07, 2008 4:38 PM
> To: [email protected]
> Subject: [flexcoders] Accessing webservice with flex
> 
>  
> 
> 
> I have a flex app (on Flex 3) hosted on our server which is trying to
> access
> data through a webservice call. 
> I recently upgraded my flash player from version 9 to version 10. When I
> am
> trying to access my webservice it gives me the Channel.Security.Error . 
> I tried to look for a solution to this problem and found that it had to
> do
> with the crossdomain.xml file which is in the same folder as my project
> on
> the server. This is how our file looks 
> 
> <?xml version="1.0"?> 
> <!DOCTYPE cross-domain-policy SYSTEM
> "http://www.macromedia.com/xml/dtds/cross-domain-policy.dtd
> <http://www.macromedia.com/xml/dtds/cross-domain-policy.dtd> "> 
> <cross-domain-policy> 
> <site-control permitted-cross-domain-policies="all"/> 
> <allow-access-from domain="*" to-ports="*" secure="true" /> 
> <allow-http-request-headers-from domain="*" headers="*" secure="true" />
> 
> </cross-domain-policy> 
> 
> Could anyone please help me with this error. Its getting really
> frustrating.
> -- 
> View this message in context:
> http://www.nabble.com/Accessing-webservice-with-flex-tp20389372p20389372
> .html
> <http://www.nabble.com/Accessing-webservice-with-flex-tp20389372p2038937
> 2.html> 
> Sent from the FlexCoders mailing list archive at Nabble.com.
> 
>  
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Accessing-webservice-with-flex-tp20389372p20445599.html
Sent from the FlexCoders mailing list archive at Nabble.com.

Reply via email to