<?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 Re: URL Redirection in Cisco ASA in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/url-redirection-in-cisco-asa/m-p/1805874#M496439</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Since both are https, I dont think why not, you can try something like this: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Object network obj-x.x.x.x&lt;/P&gt;&lt;P&gt;&amp;nbsp; host x.x.x.x &lt;/P&gt;&lt;P&gt;Object network obj-y.y.y.y&lt;/P&gt;&lt;P&gt; host y.y.y.y&lt;/P&gt;&lt;P&gt;Object service https &lt;/P&gt;&lt;P&gt;&amp;nbsp; service tcp destination eq 443 &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;and then create something like this &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;nat (inside,outside) source dynamic any interface destination static obj-x.x.x.x obj-y.y.y.y service&amp;nbsp; https &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;That will cause everyone to be natted to the outside interface and then the destination is going to be changed from x.x.x.x to y.y.y.y on the service specified.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Try that out and let me know... &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mike &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 06 Oct 2011 04:38:44 GMT</pubDate>
    <dc:creator>Maykol Rojas</dc:creator>
    <dc:date>2011-10-06T04:38:44Z</dc:date>
    <item>
      <title>URL Redirection in Cisco ASA</title>
      <link>https://community.cisco.com/t5/network-security/url-redirection-in-cisco-asa/m-p/1805873#M496438</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a cisco ASA box with 8.3 code running on it. My setup is very simple as below -&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Users---&amp;gt;Switch--&amp;gt;ASA--&amp;gt;Internet&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There is a website x.x.x.x which is on internet, users access this website through browser as &lt;A href="https://x.x.x.x" target="_blank"&gt;https://x.x.x.x&lt;/A&gt;. DNS entry for this url is done on internet and our local DNS server gets this entry from ISP DNS server. Now, there is a new version of this website which is launched as &lt;A href="https://y.y.y.y" target="_blank"&gt;https://y.y.y.y&lt;/A&gt; , we want that anybody who access x.x.x.x should be redirected to y.y.y.y (for https or for all port).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This requirement can be fulfilled in Cisco ASA??? in simple terms we want url redirection.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Ahmed&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 21:34:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/url-redirection-in-cisco-asa/m-p/1805873#M496438</guid>
      <dc:creator>nuruddin.ahmed</dc:creator>
      <dc:date>2019-03-11T21:34:24Z</dc:date>
    </item>
    <item>
      <title>Re: URL Redirection in Cisco ASA</title>
      <link>https://community.cisco.com/t5/network-security/url-redirection-in-cisco-asa/m-p/1805874#M496439</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Since both are https, I dont think why not, you can try something like this: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Object network obj-x.x.x.x&lt;/P&gt;&lt;P&gt;&amp;nbsp; host x.x.x.x &lt;/P&gt;&lt;P&gt;Object network obj-y.y.y.y&lt;/P&gt;&lt;P&gt; host y.y.y.y&lt;/P&gt;&lt;P&gt;Object service https &lt;/P&gt;&lt;P&gt;&amp;nbsp; service tcp destination eq 443 &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;and then create something like this &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;nat (inside,outside) source dynamic any interface destination static obj-x.x.x.x obj-y.y.y.y service&amp;nbsp; https &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;That will cause everyone to be natted to the outside interface and then the destination is going to be changed from x.x.x.x to y.y.y.y on the service specified.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Try that out and let me know... &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mike &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 06 Oct 2011 04:38:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/url-redirection-in-cisco-asa/m-p/1805874#M496439</guid>
      <dc:creator>Maykol Rojas</dc:creator>
      <dc:date>2011-10-06T04:38:44Z</dc:date>
    </item>
    <item>
      <title>URL Redirection in Cisco ASA</title>
      <link>https://community.cisco.com/t5/network-security/url-redirection-in-cisco-asa/m-p/1805875#M496442</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; Dear maykol,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for your response, i would definetly try this and let you know the outcome but i have one more query on this. the above nat soolution, which you have given, will take precedence over existing PAT???&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 06 Oct 2011 12:59:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/url-redirection-in-cisco-asa/m-p/1805875#M496442</guid>
      <dc:creator>nuruddin.ahmed</dc:creator>
      <dc:date>2011-10-06T12:59:40Z</dc:date>
    </item>
    <item>
      <title>Hi guys,</title>
      <link>https://community.cisco.com/t5/network-security/url-redirection-in-cisco-asa/m-p/1805876#M496446</link>
      <description>&lt;P&gt;Hi guys,&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Did you get the URL redirection to work?&lt;/P&gt;</description>
      <pubDate>Fri, 21 Oct 2016 15:11:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/url-redirection-in-cisco-asa/m-p/1805876#M496446</guid>
      <dc:creator>Davion Stewart</dc:creator>
      <dc:date>2016-10-21T15:11:07Z</dc:date>
    </item>
  </channel>
</rss>

