Flex 应用程序中 crossdomain.xml 的协议错误

发布于 2024-09-28 02:54:46 字数 327 浏览 3 评论 0原文

我已将 Flex 应用程序的协议从 https 更改为 http,并且 flashplayer 仍然希望使用 https 下载 crossdomain.xml,尽管端口为 http。 该应用程序通过 http://domain01:8080/flex 访问,并且想要获取 https:..samedomain。 .:8080/crossdomain.xml (在 https:..samedomain..no_port/flex 工作正常)。

有人知道为什么吗?

非常感谢,

丹尼尔

I've changed the protocol for my flex app from https to http and flashplayer still wants to download the crossdomain.xml using https though with the port for http.
the app is accessed at http://domain01:8080/flex and it wants to get https:..samedomain..:8080/crossdomain.xml (at https:..samedomain..no_port/flex it works fine).

Anyone any idea why?

Thanks a lot,

Daniel

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(3

眼角的笑意。 2024-10-05 02:54:46

没有直接的答案,因为我还没有尝试过指定非默认端口的这种情况,但有一些信息可能会引导您找到答案:

http://learn.adobe.com/wiki/download/attachments/64389123/CrossDomain_PolicyFile_Specification.pdf?version=1

这个可能感兴趣:

<?xml version="1.0"?>
<!DOCTYPE cross-domain-policy SYSTEM
"http://www.adobe.com/xml/dtds/cross-domain-policy.dtd">
<cross-domain-policy>
   <allow-access-from domain="*.example.com" to-ports="507,516-523"/>
</cross-domain-policy>

或者这个:

10,0,12,0 site-control's allowed-cross-domain-policies default for non-socket policy files is "master-only"

也许尝试旧版本的 Flash Player 看看是否有什么9->10 的更改导致了问题,那么在更改日志中查找更改可能会更容易,或者可能是新版本中的错误。

祝你好运
肖恩

No direct answer as I haven't tried this scenario of specifying a non-default port but a couple of piece of info that might lead you to an answer:

http://learn.adobe.com/wiki/download/attachments/64389123/CrossDomain_PolicyFile_Specification.pdf?version=1

This might be of interest:

<?xml version="1.0"?>
<!DOCTYPE cross-domain-policy SYSTEM
"http://www.adobe.com/xml/dtds/cross-domain-policy.dtd">
<cross-domain-policy>
   <allow-access-from domain="*.example.com" to-ports="507,516-523"/>
</cross-domain-policy>

or this:

10,0,12,0 site-control's permitted-cross-domain-policies default for non-socket policy files is "master-only"

Maybe try an older version of Flash Player to see if something in the changes from 9->10 is causing the issue then finding the change in the change logs might be easier or perhaps it's a bug in the new version.

Good luck
Shaun

酒几许 2024-10-05 02:54:46

Flex(至少 3.5 AFAIK..)在更改端口并使用 Https 时会遇到一些识别危机...安全模型取决于端口..我不知道问题的确切原因,但我的解决方案是加载跨域明确地在您的应用程序中文件..

System.security.loadPolicyFile('https://mydomain:port/crossdomain.xml');

Flex (Atleast 3.5 AFAIK..) gets some identify crisis when you change port and use Https... The security model depends on the port.. I do not know the exact reason for the problem, but my solution was to load the crossdomain file in your app explicitly..

System.security.loadPolicyFile('https://mydomain:port/crossdomain.xml');

多情癖 2024-10-05 02:54:46

当您遇到跨域问题时,值得记住的是,通过使用 Security 类,您始终可以显式控制加载的 crossdomain.xml 文件(事实上,策略文件可以具有您想要的任何名称)。在处理更复杂的实际情况(例如,使用负载平衡或反向代理)时,从服务器根加载策略文件的默认行为通常限制过多。

尝试使用:

Security.loadPolicyFile(<URI to the policy file goes here>);

ASDocs 是 here 并对其进行了很好的解释。

通过控制策略的加载方式,您可以获得更多自由消除大量猜测,否则可能会是痛苦、令人沮丧的体验。 Flash Player 允许您加载多个策略文件,如果您需要与多个服务层集成(例如,在一台主机上通过 HTTPS,在另一台主机上通过 HTTP)集成,这会很方便。

祝你好运,

泰勒

When you run into crossdomain issues, it's worth remembering that by using the Security class, you can always take explicit control over what crossdomain.xml file is loaded (in fact, the policy file can have any name you want). The default behavior of loading the policy file from the root of a server can often be too restrictive when dealing with more complex, real-world cases (with load-balancing or reverse proxies, for instance).

Try using:

Security.loadPolicyFile(<URI to the policy file goes here>);

The ASDocs are here and explain it quite well.

By taking control of how policies are loaded, you can gain more freedom and take a lot of the guesswork out of what can otherwise be a painful, frustrating experience. The Flash Player allows you to load multiple policy files which is handy if you need to integrate with more than one service layer (e.g. on one host through HTTPS and another through HTTP).

Good luck,

Taylor

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文