Supportability of rewrites and redirects in sharepoint 2016 2013 2010 and 2007

Summary

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.

Some of these tools may function as expected when you use them to configure a URL rewrite or redirect that is related to SharePoint. However, when you evaluate the supportability for any URL manipulation tool that you use together with SharePoint, you should consider that Microsoft has not thoroughly tested all possible implementation scenarios that use such tools.

Important: Microsoft cannot endorse these tools or provide support for their implementation when they are used in conjunction with SharePoint.

More information

The following information is provided to show how SharePoint functions in general when you use URL rewriting and redirection.

Common URL components

Scheme	Host	Path	Query string
HTTP	www.contoso.com	/apps/default.aspx	?user=admin

There are two main types of URL changes: Rewrite and Redirect.

Rewriting modifies the incoming URL, the outgoing URL, or both. 

Redirection uses HTTP status codes such as 301 or 302 to redirect the client to a different location. This involves an additional client round trip.

Microsoft does not support implementations of any URL modification in Microsoft SharePoint Server 2016, Microsoft SharePoint Server 2013, Microsoft SharePoint Server 2010, or Microsoft Office SharePoint Server 2007.

Example Scenarios

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.

• ASYMMETRICAL REWRITE URL

  • Client makes a request to http://www.contoso.com/sites/site1

  • IIS with ARR receives the request to http://www.contoso.com/sites/site1

  • ARR uses URL Rewrite to change the URL to http://www.contoso.com/site1

  • The updated URL is then sent to the SharePoint web application.

This scenario is NOT SUPPORTED.

• SYMMETRICAL REWRITE URL

  • Client makes a request to http://www.contoso.com/sites/site1.

  • IIS with ARR receives the request to http://www.contoso.com/sites/site1.

  • ARR uses URL Rewrite to change the URL to http://www.fabrikam.com/sites/site1, and then sends the new URL to the server

  • SharePoint receives the new URL and processes it as http://www.fabrikam.com/sites/site1

This scenario is SUPPORTED.

• HTTP REDIRECT

  • Client makes a request to http://www.contoso.com/sites/site1.

  • IIS with ARR receives the request to http://www.contoso.com/sites/site1.

  • ARR uses URL Rewrite to create a redirect to http://www.fabrikam.com/sites/site1, and then returns the HTTP redirect (for example, 301 or 302) to the client

  • Client receives the redirect, and then makes a new request by using the new URL: http://www.fabrikam.com/sites/site1.

  • SharePoint receives the request, and processes it as usual.

This scenario is SUPPORTED.

For more information, see the "Reverse Proxy Publishing" section in the following TechNet topic:

   Plan Alternate Access Mapping (Office SharePoint Server)

Although the topic mentions Office SharePoint Server 2007, it also applies to SharePoint 2016, SharePoint 2013, and SharePoint 2010.