问题描述
我有一个在FlashPlayer 9中运行良好的FLEX 3前端.但是，既然我已经升级到FlashPlayer10，则?_ method = PUT/DELETE hack不再起作用.所有这些请求现在都在后端显示为POST.我做了一些阅读，听起来我需要使用as3httpclientlib并运行套接字策略服务器以提供对端口80(或任何其他端口)的访问权限，才能使用as3httpclientlib.所以我的问题是:你是在骗我吗?在早期版本的Flex/flash Player中，我要做的就是在URL中添加一个简单的字符串("_method =").但是现在我必须做曲棍球曲棍球并扭转自我?真的吗?请有人告诉我，我完全错了，事实上_method =仍然受支持.否则，它的BYE BYE FLEX/FLASH PLAYER-再也不会！
I have a FLEX 3 frontend that worked fine in FlashPlayer 9. But now that I've upgraded to FlashPlayer10, the ?_method=PUT/DELETE hack is not working anymore. All those requests show up as a POST on the backend now. I did some reading and it sounds like I need to use as3httpclientlib AND run a socket policy server to give access to port 80 (or any other port) in order to use as3httpclientlib. So my question is: are you freakin kidding me? How is it that, in earlier versions of Flex/flash player, all I had to do was add a simple string ("_method=") to the url. But now I have to do the hokey pokey AND turn my self around? Really? Please someone tell me that I've got this all wrong, and that _method= is, in fact, still supported. Otherwise, its BYE BYE FLEX/FLASH PLAYER - NEVER AGAIN!
推荐答案
我非常了解您，我的朋友，在Adobe的一项新安全策略中，身份验证标头也有类似的问题.无论如何，如果您可以共享代码，也许我可以为您提供帮助，因为您的目标在Buddy中并未明确说明.所以请让我知道，因为在这种情况下，java sandbox和silverlight并不是更好的方法.但是也许一些JavaScript东西可以节省我们的时间.
I understand you very much, my friend, just had similar noise with authentication headers in new one Security Policy from Adobe. Anyway, if you'll share your code, maybe I could help you, because your goal is not clearly explained in your post, Buddy. So let me know please, cause java sandbox and silverlight are not the better way in this case. But maybe some javascript stuff could save our time.
这篇关于Flash Player 9与带有FLEX 3的Flash Player 10，?_ method = PUT/DELETE不起作用?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！