从 SharePoint URL 中取出 /Pages？
一位客户询问我们是否可以采取任何措施从他面向 Internet 的 MOSS 发布站点中删除“/Pages”。 一些谷歌搜索显示，HTTPModules 的一些巧妙使用可能能够隐藏页面的存在，但我还没有看到端到端的工作解决方案。 你们中有人遇到过这个特殊的要求吗？如果有，您是如何解决的？
客户对 /Pages 的主要关注点是它对 SEO 的影响 - 如果有人有任何方法可以缓解这些问题，或者可以解释为什么在您的 URL 中添加这个额外级别不会成为问题，我们也会很感激（并且可能更好） ， 从长远来看！）
A customer is asking if there is anything we can do to remove "/Pages" from his Internet-facing MOSS publishing site. Some Googling reveals that some clever use of HTTPModules may be able to hide the presence of Pages, but I've yet to see an end-to-end working solution. Have any of you come up against this particular requirement, and if so, how did you resolve it?
The customer's main concern with /Pages is the SEO impact of it - if anyone has any way to mitigate those issues or can explain why having this extra level in your URL would not be a concern, that would be appreciated as well (and probably better, in the long run!)
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（5）
查看此帖子。 http://blog .mastykarz.nl/semantic-urls-in-moss-2007-imtech-sharepoint-semantic-urls-free-feature/
Check out this posting. http://blog.mastykarz.nl/semantic-urls-in-moss-2007-imtech-sharepoint-semantic-urls-free-feature/
您将遇到的主要问题是 Microsoft 不会为“隐藏”页面库的 SharePoint 实例提供支持。
是的，您可以使用 URL 重写器来排除路径的 /pages 部分，并且您还需要对响应流执行搜索和替换，以将其从所有生成的 URL 中剥离 - 这显然会提高性能命中服务器 - 但如果仔细使用缓存，它可能不会那么明显。
PSS 将要求您删除设置，然后他们才会调查您网站的任何问题，因此您（或您的客户）需要权衡性能和支持问题的感知优势。
我相信我们过去已经为我们的一位客户做到了这一点，但大多数人都乐意坚持使用 /pages 元素 - 它确实没有那么大的效果。
The main issue you'll have is that Microsoft won't provide support for a SharePoint instance that has "hidden" the pages library.
Yes, you can use a URL re-writer to exclude the /pages section of the path, and you will also need to perform a search and replace on the response stream to strip it out of all generated URLS - this will obviously have a performance hit on the server - but with careful use of caching, it might not be that noticable.
PSS will require you to remove the setup before they will investigate any issues with your site, so you (or your client) will need to weigh up the perceived benefits with the performance and support issues.
I believe we've done it for one of our clients in the past, but most are happy to stick with the /pages element - it really doesn't have that much effect.
我知道 ASP.NET 3.5 SP1 具有 ASP.NET MVC 内置的 URL 路由引擎。如果您想针对该版本的 .NET 框架运行，您可以使用路由来消除 URL 的 /Pages 部分。 但我对在该版本的 .NET 上运行 MOSS 持怀疑态度。 不过，这是我要检查的第一个地方。
I know ASP.NET 3.5 SP1 has the URL routing engine that ASP.NET MVC uses built in. If you wanted to run against that version of the .NET framework, you could use routes to eliminate the /Pages part of the URL. But I'm not positive about running MOSS on that version of .NET. That's the first place I'd check, though.
您可以在此处使用 MOSS 获取面向公众的网站列表。 您可以看到他们使用“页面”库，并且您可以根据内容检查您最喜欢的搜索引擎。
希望这足以证明“页面”库不会成为太大的问题，并且您可以为他们节省大量现金。
You can get a list of public facing websites using MOSS here. You can see they use the "page" libraries and you can check your favorite search engines against the content.
Hopefully this will be enough to demonstrate that the "Page" libraries aren't going to be too much of an issue and you can save them a bunch of cash.
您可以更改 /Pages 库的名称（和 url）。
You can change the name (and the url) of the /Pages library.