Article ID: 2818415 - View products that this article applies to.
This article summarizes the supportability impact of URL rewriting and redirection options using any of the URL manipulation tools in conjunction with SharePoint (i.e. URL Rewrite).
There is no single answer when evaluating the supportability for any URL manipulation tools in conjunction with SharePoint. While some of these tools may function as expected when used in conjunction with SharePoint, without testing specific scenarios we cannot endorse or provide support for them when used in conjunction with SharePoint. these tools cannot be made as the implementation scenarios have not been tested thoroughly. However, the following information, along with examples should help you to understand how SharePoint functions in general when using URL rewriting and redirection.
Common URL components:
There are two main types of URL modifications:
Redirection is the use of HTTP status codes 301 or 302 to redirect the client to a different location, which involves an additional client round trip.
Rewriting is actually changing both incoming and/or outgoing URLs. Any implementation of such rewrites is unsupported with SharePoint unless the path is symmetrical.
For example, you can modify the path of a request, such as http://www.contoso.com/sharepoint/default.aspx, which is forwarded to the SharePoint server as http://sharepoint.perimeter.example.com/default.aspx. This is referred to as an asymmetrical path.
SharePoint Server 2007/2010/2013 do NOT support asymmetrical paths. The path of the URL must be symmetrical between the public URL and the internal URL. In the above example, this means that the /SharePoint/default.aspx portion of the URL must not be modified by any external tool.
Example Scenarios (All scenarios below use ARR as the proxy and use URL Rewrite to modify the URL)
This scenario is NOT SUPPORTED.
This scenario is SUPPORTED. NOTE: Hostname, port number, protocol changes are all supported in Symmetrical Rewrites
This scenario is SUPPORTED.For more information, see Reverse Proxy Publishing section under Plan Alternate Access Mappings article in TechNet. Although the article mentions Office SharePoint Server 2007, it is also applicable to SharePoint 2010 and SharePoint 2013.
Article ID: 2818415 - Last Review: May 15, 2013 - Revision: 6.0