3 Replies Latest reply on Oct 18, 2006 8:18 PM by wrench

    understanding crossdomain.xml

    dan_mcgowan
      Hi,
      I am a noob with flex. So I have two sample web services apps that use mx:WebService. Both work fine in the flex builder environment. But only one works after deployment to my apache server. I have a wildcard "*" crossdomain.xml deployed off of my apache document root. The web service that works is the "blogger" sample app from the flex docs. It deploys fine. That service is:

      http://weblogs.macromedia.com/mchotin/index.xml

      and http://weblogs.macromedia.com/crossdomain.xml is also wide open:

      <cross-domain-policy>
      <allow-access-from domain="*"/>
      </cross-domain-policy>

      The other app uses one of the demo xmethod services:

      http://services.xmethods.net/soap/urn:xmethods-delayed-quotes.wsdl

      and http://services.xmethods.net/crossdomain.xml is wide open too:

      <cross-domain-policy>
      <allow-access-from domain="*"/>
      </cross-domain-policy>

      Again works fine from the builder, but after deployed to apache, the app crokes when attempting to access the web service. The ever-popular error message:

      [RPC Fault faultString="Security error accessing url" faultCode="Channel.Security.Error" faultDetail="Destination: DefaultHTTP"]...

      Any insights on why this app has the issue when the other one is fine? Thank for your help,

      Dan