4 Replies Latest reply on Mar 13, 2009 6:59 AM by atlantageek

    Crossdomain

    mcemonkey Level 1
      Here is the problem: Client has a WSDL running on port 8080 of their server, this port does not accept GET's so you can only POST to the WSDL. The first thing I did was put a crossdomain.xml on the normal HTTP port 80, which failed to allow me access to port 8080. I also tried allow-access-from domain="*" to-ports="80,8080" which also did not allow me access to port 8080.
      my policyfiles.txt log is quoted below.

      The next thing I tried was to have them setup a policy file server. After a lot of trouble with adobes perl script outputting the status text to the socket I had it up and running.
      I used this policyfile:[attached]

      Which is no different then the one I used on the HTTP side. That let me make socket connections but when I tried to POST to the WSDL I got the same thing! searching for allow ect then it tries to load a crossdomain off the 8080 port which is impossible.
      After 2 days of back and forth with a client working with their tech to implement a valid crossdomain file/policy server I am absolutely stumped and very frustrated. Can someone please help me out here I am sinking fast.

      quote:

      OK: Policy file accepted: http://removed/crossdomain.xml
      OK: Searching for allow-access-from in policy files to authorize data loading from resource at http://removed/wsdl?wsdl by requestor from http://removed/testview.swf
      OK: Searching for allow-http-request-headers-from in policy files to authorize header sending to URL http://removed/wsdl?wsdl by requestor from http://removed/testview.swf
      Warning: Failed to load policy file from http://removed:8080/crossdomain.xml