Seems that this is a flash player 10 issue (see: http://issues.ez.no/IssueView.php?Id=13783 and http://ez.no/developer/forum/general/flash_player_10_swf_files_ez_publish_4_problem ). Flash player 10 doesnt like content-disposition attachment header anymore, theese headers are sent if the files are delivered via content/download/..
A solution is to either apply the patch in the issue tracker or to ovverride the flash-template and use the real-url of the swf instead of content/download..
thanks for the quick reply. I installed the patch without success.
I checked the flash version I was running in all the other browsers that work fine (Sea monkey, IE7 and Opera) and it is 10,0,12,36. So it apprears to work with flash version 10 in other browsers??
are you sure your other browsers had flash 10 plugin installed? Actually flash player 10 should behave the same in all browsers on all platforms (its a new security feature ;-) they implemented a lot of very restrictive stuff in 10.x). See: http://www.adobe.com/devnet/flashplayer/articles/fplayer10_security_changes_02.html
I also had problems with the patch, try to only add the following line
This worked for me, although I dont like these kernel modifications. Again, a much better and cleaner solution would be to override the template and replace the content/download part with the direct url of the swf. Than your webserver will serve the file directly.
you are definitely right, I will do so after investigation why the patch doesnt work for me (didnt find the time for that yet). Obviously the function dispositionType returns "attachment", so the problem must be either there or in my file.ini ..
I'm not sure if this is relevant, but apart from the latest flash attachment disposition fix, we've experienced some problems with the new SWFObject 2.0. It appeared to be even a greater problem, and we had to switch to 1.5, which brought back stability.
I haven't investigated this too much, but maybe someone has more information or maybe this will solve your problems, as well.