<?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 HTTP redirect url from NATed server in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/http-redirect-url-from-nated-server/m-p/1658586#M536346</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This could be fixed on your webserver itself , It could be worthwhile if you could give an emaple of the published URL and the redirected one ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When the client responds with teh URL its the domain name that should be gettign resolved from the cilents dns server .&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 14 Jul 2011 10:31:30 GMT</pubDate>
    <dc:creator>Siju S</dc:creator>
    <dc:date>2011-07-14T10:31:30Z</dc:date>
    <item>
      <title>HTTP redirect url from NATed server</title>
      <link>https://community.cisco.com/t5/network-security/http-redirect-url-from-nated-server/m-p/1658584#M536344</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have a scenario where webserver in DMZ is NATed to public IP Address on outside. Now, when client initiates the session, request goes to the webserver and webserver replies back to the client with a redirect URL that contains the real IP Address of the webserver and not the NATed IP. This could be seen in the client address bar. Client connection drops.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there a way to rewrite the URL so that it gets the NATed IP Address instead of the real one.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Saif&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 20:57:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/http-redirect-url-from-nated-server/m-p/1658584#M536344</guid>
      <dc:creator>saifuddin.miyaji</dc:creator>
      <dc:date>2019-03-11T20:57:10Z</dc:date>
    </item>
    <item>
      <title>HTTP redirect url from NATed server</title>
      <link>https://community.cisco.com/t5/network-security/http-redirect-url-from-nated-server/m-p/1658585#M536345</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Saif,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Could you share your configuration here?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Anu&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 11 Jul 2011 14:47:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/http-redirect-url-from-nated-server/m-p/1658585#M536345</guid>
      <dc:creator>Anu M Chacko</dc:creator>
      <dc:date>2011-07-11T14:47:23Z</dc:date>
    </item>
    <item>
      <title>HTTP redirect url from NATed server</title>
      <link>https://community.cisco.com/t5/network-security/http-redirect-url-from-nated-server/m-p/1658586#M536346</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This could be fixed on your webserver itself , It could be worthwhile if you could give an emaple of the published URL and the redirected one ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When the client responds with teh URL its the domain name that should be gettign resolved from the cilents dns server .&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 14 Jul 2011 10:31:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/http-redirect-url-from-nated-server/m-p/1658586#M536346</guid>
      <dc:creator>Siju S</dc:creator>
      <dc:date>2011-07-14T10:31:30Z</dc:date>
    </item>
  </channel>
</rss>

