<?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 Direct traffic based on source URL in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/direct-traffic-based-on-source-url/m-p/1733165#M495525</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am glad the DNS doctoring document help you.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You do not have to worry regarding the URL issue, the set up is going to work, I believe that at this moment you have 2 domain names for those servers on the dmz&amp;nbsp; and each domain name is linked to an IP address so anyone on the outside is going to be able to access the webserver using the URL.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 17 Oct 2011 05:03:49 GMT</pubDate>
    <dc:creator>Julio Carvajal</dc:creator>
    <dc:date>2011-10-17T05:03:49Z</dc:date>
    <item>
      <title>Direct traffic based on source URL</title>
      <link>https://community.cisco.com/t5/network-security/direct-traffic-based-on-source-url/m-p/1733160#M495514</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Has anyone configured their Cisco ASA to do port based forwarding based on the incoming URL address? By this I mean lets say I have a web page hosted on the Internet with two links 1) &lt;A href="https://community.cisco.com/www.website1.com" target="_blank"&gt;www.website1.com&lt;/A&gt; 2) &lt;A href="www.website2.com.&amp;nbsp;" target="_blank"&gt;www.website2.com.&amp;nbsp;&lt;/A&gt; Let's assume I have a Cisco ASA with a single useable IP address to the Internet (OUTSIDE interface).&amp;nbsp; I also have two web servers on the DMZ interface on the same ASA.&amp;nbsp; Is it possible to configure the ASA to port foward incoming traffic to a particular DMZ web host (port 80) based on the link they clicked?&amp;nbsp; So if a user click on link &lt;A href="https://community.cisco.com/www.website1.com" target="_blank"&gt;www.website1.com&lt;/A&gt; then traffic would be fowarded to DMA web server1 and if the same user clicks on &lt;A href="https://community.cisco.com/www.website2.com" target="_blank"&gt;www.website2.com&lt;/A&gt; then the ASA would direct traffic to DMZ web server2?&lt;/P&gt;&lt;P&gt;Note that in this scenario only a single ip address exists to the Internet. Can this be done with static NAT'ing?&amp;nbsp; Running 8.2.2 firmware.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance.&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 21:38:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/direct-traffic-based-on-source-url/m-p/1733160#M495514</guid>
      <dc:creator>Michael Kim</dc:creator>
      <dc:date>2019-03-11T21:38:31Z</dc:date>
    </item>
    <item>
      <title>Direct traffic based on source URL</title>
      <link>https://community.cisco.com/t5/network-security/direct-traffic-based-on-source-url/m-p/1733161#M495517</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Lets say Outside Ip address is 162.10.10.2,DMZ_Server_1 is 192.168.10.2, DMZ_Server_2 is 192.168.10.3.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So the configuration on 8.2.2 required to allow this would be:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Static (Dmz,outside) tcp interface 80 192.168.10.2 80&lt;/P&gt;&lt;P&gt;Static (Dmz,outside) tcp interface 8080&amp;nbsp; 192.168.10.3 80&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Access-list outside_in permit tcp any host 162.10.10.2 eq 80&lt;/P&gt;&lt;P&gt;Access-list outside_in permit tcp any host 162.10.10.2 eq 8080&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Access-group outside_in in interface outside&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Have a great day,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Julio&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 17 Oct 2011 02:00:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/direct-traffic-based-on-source-url/m-p/1733161#M495517</guid>
      <dc:creator>Julio Carvajal</dc:creator>
      <dc:date>2011-10-17T02:00:24Z</dc:date>
    </item>
    <item>
      <title>Direct traffic based on source URL</title>
      <link>https://community.cisco.com/t5/network-security/direct-traffic-based-on-source-url/m-p/1733162#M495519</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for the reply Julio.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Question: Based on the config you have given above how does the ASA know that to which DMZ web server to direct the incoming connection?&amp;nbsp; To put it another way if a user types into their browser &lt;A href="https://community.cisco.com/www.website2.com" target="_blank"&gt;www.website2.com&lt;/A&gt; how does the ASA determine that it should go to 192.168.10.3 instead of 192.168.10.2?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I was half expecting that the ASA would "read" the URL address and use that as a determination to direct the incoming connection to the apporpriate DMZ web server.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mike&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 17 Oct 2011 02:16:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/direct-traffic-based-on-source-url/m-p/1733162#M495519</guid>
      <dc:creator>Michael Kim</dc:creator>
      <dc:date>2011-10-17T02:16:18Z</dc:date>
    </item>
    <item>
      <title>Direct traffic based on source URL</title>
      <link>https://community.cisco.com/t5/network-security/direct-traffic-based-on-source-url/m-p/1733163#M495521</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The thing is that as long as I know the ASA cannot make portforwarding based on an URL. That is why we would need to use the IP address of the webserver.&lt;/P&gt;&lt;P&gt;Now each domain has an Ip address right, that is why we use the Domain name system(DNS),and in this case 192.168.10.2 and .3 are going to be linked to&amp;nbsp; &lt;A href="https://community.cisco.com/www.website1.com" target="_blank"&gt;www.website1.com&lt;/A&gt; and&amp;nbsp; www.website2.com.&lt;/P&gt;&lt;P&gt;So as soon as the ASA sees a request going to those address is going to redirect the traffic to that server.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;By the way if you want to access these servers from the inside network or the DMZ network using the Public IP you will need to do DNS Doctoring.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here is one document that explains this Feature ( DNS doctoring)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.techrepublic.com/blog/networking/cisco-asa-and-dns-pain-is-there-a-doctor-in-the-house/1140"&gt;http://www.techrepublic.com/blog/networking/cisco-asa-and-dns-pain-is-there-a-doctor-in-the-house/1140&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Julio&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 17 Oct 2011 02:43:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/direct-traffic-based-on-source-url/m-p/1733163#M495521</guid>
      <dc:creator>Julio Carvajal</dc:creator>
      <dc:date>2011-10-17T02:43:58Z</dc:date>
    </item>
    <item>
      <title>Direct traffic based on source URL</title>
      <link>https://community.cisco.com/t5/network-security/direct-traffic-based-on-source-url/m-p/1733164#M495523</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It's disappointing that the ASA can not port foward traffic from the outside based on URL.&amp;nbsp; We are currently using a Microsoft ISA server that is able to direct traffic based upon the source URL (so i'm told). &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for the link on DNS Doctoring as that was another issue I was going to try and tackle.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mike&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 17 Oct 2011 02:56:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/direct-traffic-based-on-source-url/m-p/1733164#M495523</guid>
      <dc:creator>Michael Kim</dc:creator>
      <dc:date>2011-10-17T02:56:01Z</dc:date>
    </item>
    <item>
      <title>Direct traffic based on source URL</title>
      <link>https://community.cisco.com/t5/network-security/direct-traffic-based-on-source-url/m-p/1733165#M495525</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am glad the DNS doctoring document help you.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You do not have to worry regarding the URL issue, the set up is going to work, I believe that at this moment you have 2 domain names for those servers on the dmz&amp;nbsp; and each domain name is linked to an IP address so anyone on the outside is going to be able to access the webserver using the URL.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 17 Oct 2011 05:03:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/direct-traffic-based-on-source-url/m-p/1733165#M495525</guid>
      <dc:creator>Julio Carvajal</dc:creator>
      <dc:date>2011-10-17T05:03:49Z</dc:date>
    </item>
  </channel>
</rss>

