|What about CKS:EBE? Obviously, I’m a fan. I wouldn’t publish to a public SharePoint blog without it. The SEO benefits are enough for me to risk the supportability. Plus, I’m not the admin on this box. :;
Seriously though, this blog, running Enhanced Blog Edition had the number one hit for SharePoint 2010 for 6 months after that was announced as the official product name. Currently, #3 on bing for sharepoint bing maps That’s some serious Google and Bing karma!
Grain of salt: This is custom code that may not be seen as easily removed. Even though you can configure CKS:EBE to not use the rewriting the code still exists in the assembly deployed to the farm.
Official Microsoft Statement
|The official word on modifying the path of a SharePoint URL was pointed out to me by a friend, thanks Maurice. Read TechNet Article CC288609 and pay close attention to the following:
|Some reverse proxy devices can modify the path of a request (the portion of the URL that comes after the hostname and port number) in such a way that a request sent by the user to http://www.contoso.com/sharepoint/default.aspx, for example, is forwarded to the Web server as http://sharepoint.perimeter.example.com/default.aspx.
This is referred to as an asymmetrical path. Windows SharePoint Services 3.0 does not support asymmetrical paths. The path of the URL must be symmetrical between the public URL and the internal URL. In the preceding example, this means that the “/sharepoint/default.aspx” portion of the URL must not be modified by the reverse proxy device.
If you find that Note confusing, you are not alone. I didn’t get the “you are not supported” vibe from that the first 10 times I read it. My skull is thick, but Spence has a big hammer! 🙂
Redirect all you want, rewrite with care!
The twitter conversation, from the reply side follows. Note MCM Brian Porter’s comment about redirection. This has been echoed by other experts in the field.
Doesn’t a mugs game sounds fun? Love that British English! 🙂