Comments for the source

Comment on Solving the Soap Cross Domain Problem for Flash Player 9,0,124,0 by Jason

Jason — Mon, 03 Aug 2009 23:45:32 +0000

@Ryan Are you trying to call web services that reside on some other server (not the one that your flash movie is served from)?

If so, the cross domain file needs to reside on the server that is serving the web services.

If that server is out of your control, you may need to look at using some sort of proxy or something so that your flash movie is making requests to your own server and then your server is then making requests to the web services.

Comment on Solving the Soap Cross Domain Problem for Flash Player 9,0,124,0 by Ryan

Ryan — Mon, 03 Aug 2009 23:09:32 +0000

My god, I am so frustrated with this…
I have everything working inside the flash ide… everything works smoothly…

I can not get this to work on my localhost, or my webserver… I am using Apache’s latest, with WAMP…

Why on early would this not work? I have flash 10, but every policy file that I come across has not worked for me!

Any suggestions?

my sample page is:
http://www.hungateagency.com/justin/soap

You can see that to the right of the labels there is no text responses… UGH!
Ryan

Comment on Solving the Soap Cross Domain Problem for Flash Player 9,0,124,0 by pouic

pouic — Wed, 22 Oct 2008 16:40:26 +0000

Thanks Thanks Thanks Thanks

Comment on Solving the Soap Cross Domain Problem for Flash Player 9,0,124,0 by Tayfusion

Tayfusion — Sun, 05 Oct 2008 16:19:23 +0000

Well done guys, the request headers inclusion has done the trick. Shame adobe are not so forthcoming with the resolution.

Comment on Solving the Soap Cross Domain Problem for Flash Player 9,0,124,0 by Jonas357

Jonas357 — Wed, 27 Aug 2008 07:47:31 +0000

Thanks for the help guys, much appreciated.

Comment on Flash Player 9 Update 3 and the Socket Policy File by Nathan

Nathan — Thu, 21 Aug 2008 00:15:12 +0000

From Adobe’s website: a little quicker to do:

A quick verification of the service can be done by using either Perl or Python in conjunction with the netcat utility:

python -c ‘print “%c” % 0′ | nc 127.0.0.1 843
perl -e ‘printf “%c”,0′ | nc 127.0.0.1 843

If the socket policy file is returned by running one of the above commands, then the test was successful.

Comment on Solving the Soap Cross Domain Problem for Flash Player 9,0,124,0 by Jason

Jason — Mon, 04 Aug 2008 23:57:24 +0000

Of course - I’d forgotten about requesting the WSDL!

That makes sense.

Comment on Solving the Soap Cross Domain Problem for Flash Player 9,0,124,0 by Kevin

Kevin — Mon, 04 Aug 2008 18:22:55 +0000

LUKE: Looks to me like the GET comes from the call to
_global.gameService = new WebService(”http://www.DomainName.com/PostScore.asmx?wsdl”);
Presumably, Flash is just loading the service’s WSDL. The actual processing of the WebService Call is a POST.

Thanks for this, by the way. I did waste 3 hours today messing with all sorts of things. The Headers section in the crossdomain.xml did the trick!

Kevin

Comment on Solving the Soap Cross Domain Problem for Flash Player 9,0,124,0 by Ben Morrow

Ben Morrow — Sun, 03 Aug 2008 15:56:51 +0000

Thanks!!! Hours and days is exactly right, I wish Adobe’s documentation was clearer

Comment on Solving the Soap Cross Domain Problem for Flash Player 9,0,124,0 by Josh Strike

Josh Strike — Tue, 29 Jul 2008 04:53:52 +0000

I knew there was something screwy with Wade’s tags. This problem never seemed to affect any amfphp as he’d suggested it would, so I just ignored it. It was an intermittent FileReference upload (when it was to a different subdomain) problem that wouldn’t go away that caused me to find this post…