asp:MediaPlayer (Silverlight) https/http 问题
我们有一个网站 (https://oursite.net)，我们在其中显示托管在 http (http://someserver.com）。该网站需要托管在 https 上，并且我们不控制视频，因此我假设它需要托管在 http 上。我们最近添加了通过 silverlight asp:MediaElement 播放流的选项，该选项在我们的测试环境（在 http 上）中运行得很好，但在生产环境中（https）中不起作用。
网络上的信息有点令人困惑，因为我很难区分这些东西在 silverlight 开发的不同阶段是如何工作的（似乎有点来回）
这种设置是否可能（托管播放器）在 https 上但在 http 上播放流）并使用某种策略文件？ 在这种情况下：此策略文件是否需要通过 silverlight 应用程序（在 https 上）或流所在的位置（http）
托管 安德烈亚斯
we have a site (https://oursite.net) in which we display a videostream hosted on http (http://someserver.com). The site needs to be hosted on https, and we don't control the video, so I'm assuming it needs to be on http. we recently added the option to play the stream through the silverlight asp:MediaElement, which works perfectly fine in our test environment (on http) but doesn't work in production (https).
The info on the web is somewhat confusing as I'm having a hard time differentiating between how this stuff worked at different stages in the silverlight development (seems to have been a bit to and fro)
Is this setup possible at all (hosting the player on https but playing a stream on http) with some sort of policy file?
in that case: does this policy file need to be hosted with the silverlight app (on https) or where the streams are located (http)
Thanks for your time
Andreas
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
不幸的是，您遇到了跨方案违规。该流需要与托管应用程序匹配相同的方案 (https)。不幸的是，大多数流媒体在 HTTPS 中不可用。
You are running into a cross-scheme violation unfortunately. The stream would need to match the same scheme (https) as the hosting application. Unfortunately most streaming isn't available in HTTPS.
您可以检查对象的 enableHtmlAccess 属性吗标签以确保其真实性？大多数媒体播放器最终都会使用 HTML DOM 桥与网页进行通信。
也可能存在跨方案问题：您应该尝试优化同一方案（HTTP 或 HTTPS）上的所有资产。
Can you check the enableHtmlAccess property on the object tag to make sure it is true? Most media players end up using the HTML DOM bridge to communicate with the web page.
It's also likely that there is a cross-scheme issue: you should try and optimize for all assets being on the same scheme (HTTP or HTTPS).