Article ID: 2818415 - View products that this article applies to.
This article discusses how supportability is affected if you configure URL rewrite and redirect scenarios in Microsoft SharePoint Server by using any URL manipulation tool, such as Internet Information Services (IIS) URL Rewrite.
Important Microsoft cannot endorse these tools or provide support for their implementation when they are used in conjunction with SharePoint.
The following information is provided to show how SharePoint functions in general when you use URL rewriting and redirection.
Common URL components
There are two main types of URL changes: Rewrite and Redirect. Microsoft does not support implementations of any URL modification in Microsoft SharePoint Server 2013, Microsoft SharePoint Server 2010, or Microsoft Office SharePoint Server 2007.
Redirection changes the incoming URL, the outgoing URL, or both.
Rewriting uses HTTP status codes such as 301 or 302 to redirect the client to a different location. This involves an additional client round trip.
You can change a request path, such as http://www.contoso.com/sharepoint/default.aspx. This path can be forwarded to the SharePoint server as http://sharepoint.perimeter.example.com/default.aspx. This is known as an asymmetrical path.
The path of the URL must be symmetrical between the public URL and the internal URL. In the example in the table, this means that the /SharePoint/default.aspx part of the URL must not be changed by any external tool.
Note All the scenarios in this section use the Application Request Routing (ARR) server as the proxy, and use URL Rewrite to change the URL.
For more information, see the "Reverse Proxy Publishing" section in the following TechNet topic:
Although the topic mentions Office SharePoint Server 2007, it also applies to SharePoint 2013 and SharePoint 2010.
Article ID: 2818415 - Last Review: May 27, 2015 - Revision: 8.0