Problem on implementing Flash on cross domain
Recently, we implemented a flash game which submits to our Formspring account . I managed to make this possible by creating a service in our amfPHP gateway. With all the testing done on our own servers, everything worked fine. After the application was considered bug-free, we then decided to send the files over to the client and instructed them to upload on their website. The setup is such that while the flash files will run in their website, it will just connect to the amfPHP gateway that is hosted on one of our servers whenever the form is submitted.
30 minutes after the project was launched, it was discovered the flash is not submitting the data properly. It was critical and the team informed me of the problem. Immediately, I tried debugging the problem using my Firebug plugin. I noticed that the page is calling a crossdomain.xml file on our amfPHP server and returns a 404 error (obviously because there is no such thing as a crossdomain.xml file in our server). So it came to me that I didn’t implement any call to a crossdomain.xml file inside my action script when I did the form. Then I decided to google ‘crossdomain.xml’. I found out that the furniture Elhovoflash player recently introduced a policyкомпютри on implementing flash on a cross domain setup. Without spending another minute, I created the file and uploaded it on our server. Whew! Thank God it worked already! Another lesson I learned with Flash and action scripting.
If you enjoyed this post, please consider to leave a comment or subscribe to the feed and get future articles delivered to your feed reader.
Comments
No comments yet.
Leave a comment