SharePoint 2010 CrossDomain.xml 文件
我们已将 crossdomain.xml
文件部署到 Sharepoint 2010 实例的根目录中,以定义闪存跨域策略。在 SP2007 中,这按预期工作,但在 SP2010 中,文件 name 被阻止。
如果我们将该文件重命名为 crossdomain.xml
以外的任何名称,则该文件将被提供。一旦我们将其命名为我们想要的,它就会抛出 404 错误。
有什么想法可以解决这个问题吗?我猜想现在一定有一种方法可以通过 SharePoint 本身来控制这个文件?
我一直在寻找除了将 crossdomain.xml 文件复制到 IIS 根目录之外的答案。
We have deployed a crossdomain.xml
file into the root of Sharepoint 2010 instance in order to define the flash cross domain policy. In SP2007 this worked as expected, but it SP2010 the file name is blocked.
If we rename the file anything other than crossdomain.xml
it's served. As soon as we name it what we want, it throws a 404 error.
Any ideas how to work around this? I'm guessing there must now be a way to control this file through SharePoint itself?
I've looking for an answer other than to copy the crossdomain.xml file into the root of IIS.
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
我发现了这行不通的原因。事实证明,在 SharePoint 2010 中,路径
crossdomain.xml
和clientaccesspolicy
被排除在虚拟路径提供程序之外,因此永远不会从 SharePoint 内容数据库提供服务。该代码隐藏在 Sharepoint
SPRequestModule
中(见下文)。唯一明智的解决方案是将 crossdomain.xml 文件部署到每个 Web 服务器上的 IIS 根目录,但这并不理想。I discovered the reason this doesn't work. It turns out in SharePoint 2010 the path
crossdomain.xml
andclientaccesspolicy
are excluded from the virtual path provider, and therefore will never be served from the SharePoint content database.The code is tucked away in the Sharepoint
SPRequestModule
(see below). The only sensible solution is to deploy thecrossdomain.xml
file to the root of IIS on each of the web servers, which is less than ideal.