Alternate Access Mapping (AAM) is used to identify Public URLs that could provide access to content. To avoid returning the incorrect URL and relative links, you would provide an entry, Internal URLs, that ensures that the appropriate Public URL is returned along with its relative links.
It is confirmed that there are only five,configurable, (5) Alternate Access Mappings (AAM) zones per Web Applications,each zone represents a Public URL. But, that fact doesn’t limit the number of Internal URLs. The Public Urls/zones are configured when we extend a Web Application. Or, In the event we configure host headers, per Public Url/zone, in IIS. For example, Default: www.sharepoint.info, Intranet: intranet.sharepoint.info, Internet: internet.sharepoint.info, External: external.sharepoint.info and Custom: myportal.sharepoint.info.
The configuration of the Internal Url extends the possibility to support or identify other possible route a user can take to access the content. The Internal URL acts similar to an alias in DNS.
Now, when a user browses to http://www.sharepoint.info, the web request is received by the IIS server. SharePoint will then receive the web request, see that the URL of the request is http://www.sharepoint.info, find that this URL is assigned to the SharePoint web application, and return the content from that web application.
In addition, because the http://www.sharepoint.info URL is assigned to the Internal URL pointing to the http://internet.sharepoint.info Public URL of the Internet zone, SharePoint will also generate links on the pages using the Public URL for that zone –
http://internet.sharepoint.info. This ensures that end users are routed to the proper URL when clicking on links on the page. That is, SharePoint acts similar to reverse proxy servers in that they overwrite the end user's original URL with the URL of the configured Public URLs/zones.
All in all, Alternate Access Mappings' (AAM) configurations, Internal Urls and Public Urls, tells SharePoint how to map web requests to the correct web application and site so that SharePoint can serve the correct content back to the user. It then tells SharePoint what URL the users should be taken to as they interact with SharePoint.
It is confirmed that there are only five,configurable, (5) Alternate Access Mappings (AAM) zones per Web Applications,each zone represents a Public URL. But, that fact doesn’t limit the number of Internal URLs. The Public Urls/zones are configured when we extend a Web Application. Or, In the event we configure host headers, per Public Url/zone, in IIS. For example, Default: www.sharepoint.info, Intranet: intranet.sharepoint.info, Internet: internet.sharepoint.info, External: external.sharepoint.info and Custom: myportal.sharepoint.info.
The configuration of the Internal Url extends the possibility to support or identify other possible route a user can take to access the content. The Internal URL acts similar to an alias in DNS.
Now, when a user browses to http://www.sharepoint.info, the web request is received by the IIS server. SharePoint will then receive the web request, see that the URL of the request is http://www.sharepoint.info, find that this URL is assigned to the SharePoint web application, and return the content from that web application.
In addition, because the http://www.sharepoint.info URL is assigned to the Internal URL pointing to the http://internet.sharepoint.info Public URL of the Internet zone, SharePoint will also generate links on the pages using the Public URL for that zone –
http://internet.sharepoint.info. This ensures that end users are routed to the proper URL when clicking on links on the page. That is, SharePoint acts similar to reverse proxy servers in that they overwrite the end user's original URL with the URL of the configured Public URLs/zones.
All in all, Alternate Access Mappings' (AAM) configurations, Internal Urls and Public Urls, tells SharePoint how to map web requests to the correct web application and site so that SharePoint can serve the correct content back to the user. It then tells SharePoint what URL the users should be taken to as they interact with SharePoint.
0 comments:
Post a Comment