2 Replies Latest reply on Feb 6, 2009 12:43 PM by AlHolden

    Collaborative Environment Setup

    ProjectedSurplus Level 1
      Long story short, I (CF/HTMLer) have a Denver based Flex coder to build a Flash version of my prototype HTML site which is hosted on an IIS/CF/MySql machine here in Vancouver.

      In struggling with flash security settings (and meta policy warnings), by saving the following crossdomain.xml in the wwwroot folder of the DevServer (it doesn't work when in the wwwroot/ProjectName folder) I can allow him to call an existing cfc and retrieve data.

      <?xml version="1.0"?>
      <!DOCTYPE cross-domain-policy SYSTEM
      " http://www.adobe.com/xml/dtds/cross-domain-policy.dtd">

      <cross-domain-policy>
      <site-control permitted-cross-domain-policies="master-only"/>
      <allow-access-from domain="*"/>
      </cross-domain-policy>

      However, if I change the "*" above to literally any (of the many other URL's and domain names we've tried) then his flex project properties of
      root folder: \\PC3\coldfusion8\wwwroot
      root URL: http://PC3:8500/

      are reported back with "Connection to ... halted - not permitted from http:/PC3:8500/ProjectMain/main2.swf"

      In so far as we have been stumbling around essentially in the dark for days now, is there anyone who can point us to how he might be able to develop (Flex) within his network/server but to call the cfc's on my server (ie specifying a domain in the crossdomain.xml that is in this case not a domain but rather the local networked named server "PC3" ) ?

      Frankly I am entirely lost with practically all flex/flash settings so thanks in advance, especially if I am missing something simple here . . .
        • 2. Re: Collaborative Environment Setup
          AlHolden Level 1
          Being an intermediate Flex guy, I can only repeat the mantra that I always chanted to myself whenever I encountered this issue: The name of the resource in the crossdomain.xml file must match that under which the Flex app itself is running, both server and domain. Under most situations: the resource in the URL of the browser for the page running the app.

          That said, here's a generic version of my own syntax. Note how the port is NOT in the domain attribute at all. All three lines constitute an entry for a single resource. Good luck.

          <?xml version="1.0"?>
          <cross-domain-policy>
          <allow-access-from domain="server.domain.com" to-ports="80,443,8400"/>
          <allow-access-from domain="server.domain.com" secure="false"/>
          <allow-http-request-headers-from domain="server.domain.com" headers="SOAPAction" secure="false" />
          </cross-domain-policy>