<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic X-Forwarded-Host &amp;amp; X-Original-Host in ArcGIS Enterprise Questions</title>
    <link>https://community.esri.com/t5/arcgis-enterprise-questions/x-forwarded-host-amp-x-original-host/m-p/1609577#M42100</link>
    <description>&lt;P&gt;At the moment we are migrating a customer from on-premises to Azure, without the use of any web-adaptor on the front-side.&lt;/P&gt;&lt;P&gt;It was surprising but in the Azure's Application Gateway (AAG) the defacto X-Forwarded-Host standard header is not set, but one of MS's own concoction: X-Original-Host.&lt;/P&gt;&lt;P&gt;While waiting a solution be implemented in AAG by the IT provider, we implemented for the meanwhile the following as solution on the internal Portal server:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Configured IIS, installed a Web Adaptor and IIS' URL Rewrite Module.&lt;/LI&gt;&lt;LI&gt;In IIS, under the URL Rewrite module created a Server Variable with as name "HTTP_X_FORWARDED_HOST".&lt;/LI&gt;&lt;LI&gt;In URL Rewrite created a rewrite rule where the Server Variable&amp;nbsp;HTTP_X_FORWARDED_HOST is assign a value like mynicename.mydomain.net.&lt;/LI&gt;&lt;LI&gt;After activating the rule, the IIS itself takes care that the X-Forwarded-Host is added to all requests.&lt;/LI&gt;&lt;/OL&gt;</description>
    <pubDate>Mon, 28 Apr 2025 07:36:17 GMT</pubDate>
    <dc:creator>EdgarWIparraguirre</dc:creator>
    <dc:date>2025-04-28T07:36:17Z</dc:date>
    <item>
      <title>X-Forwarded-Host &amp; X-Original-Host</title>
      <link>https://community.esri.com/t5/arcgis-enterprise-questions/x-forwarded-host-amp-x-original-host/m-p/1609577#M42100</link>
      <description>&lt;P&gt;At the moment we are migrating a customer from on-premises to Azure, without the use of any web-adaptor on the front-side.&lt;/P&gt;&lt;P&gt;It was surprising but in the Azure's Application Gateway (AAG) the defacto X-Forwarded-Host standard header is not set, but one of MS's own concoction: X-Original-Host.&lt;/P&gt;&lt;P&gt;While waiting a solution be implemented in AAG by the IT provider, we implemented for the meanwhile the following as solution on the internal Portal server:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Configured IIS, installed a Web Adaptor and IIS' URL Rewrite Module.&lt;/LI&gt;&lt;LI&gt;In IIS, under the URL Rewrite module created a Server Variable with as name "HTTP_X_FORWARDED_HOST".&lt;/LI&gt;&lt;LI&gt;In URL Rewrite created a rewrite rule where the Server Variable&amp;nbsp;HTTP_X_FORWARDED_HOST is assign a value like mynicename.mydomain.net.&lt;/LI&gt;&lt;LI&gt;After activating the rule, the IIS itself takes care that the X-Forwarded-Host is added to all requests.&lt;/LI&gt;&lt;/OL&gt;</description>
      <pubDate>Mon, 28 Apr 2025 07:36:17 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-enterprise-questions/x-forwarded-host-amp-x-original-host/m-p/1609577#M42100</guid>
      <dc:creator>EdgarWIparraguirre</dc:creator>
      <dc:date>2025-04-28T07:36:17Z</dc:date>
    </item>
  </channel>
</rss>

