<?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 Web publishing behind 501 in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/web-publishing-behind-501/m-p/965279#M938385</link>
    <description>&lt;P&gt;I have a network currently using ISA 2004.  I want to move them to PIX.  The only problem are two servers.  One server runs a site called &lt;A class="jive-link-custom" href="http://www.mydomain.com." target="_blank"&gt;www.mydomain.com.&lt;/A&gt;  The other site (hosted on an Exchange server) server.mydomain.com.  As far as the outside world is concerned, all of the traffic for mydomain.com goes to the ISA (198.88.238.x).  Once it hits the ISA it looks at the header and determines which inside server to send it to.  So - my question is, can this be replicated on a PIX 501?  I tried doing a translation rule but it didn't seem to do what I wanted.  To make a long story short, when traffic for &lt;A class="jive-link-custom" href="http://www.mydomain.com" target="_blank"&gt;www.mydomain.com&lt;/A&gt; hits the PIX I need it to go to server A.  When traffic for server.mydomain.com hits the PIX I need it to go to server B.&lt;/P&gt;</description>
    <pubDate>Mon, 11 Mar 2019 12:39:08 GMT</pubDate>
    <dc:creator>brownr0127</dc:creator>
    <dc:date>2019-03-11T12:39:08Z</dc:date>
    <item>
      <title>Web publishing behind 501</title>
      <link>https://community.cisco.com/t5/network-security/web-publishing-behind-501/m-p/965279#M938385</link>
      <description>&lt;P&gt;I have a network currently using ISA 2004.  I want to move them to PIX.  The only problem are two servers.  One server runs a site called &lt;A class="jive-link-custom" href="http://www.mydomain.com." target="_blank"&gt;www.mydomain.com.&lt;/A&gt;  The other site (hosted on an Exchange server) server.mydomain.com.  As far as the outside world is concerned, all of the traffic for mydomain.com goes to the ISA (198.88.238.x).  Once it hits the ISA it looks at the header and determines which inside server to send it to.  So - my question is, can this be replicated on a PIX 501?  I tried doing a translation rule but it didn't seem to do what I wanted.  To make a long story short, when traffic for &lt;A class="jive-link-custom" href="http://www.mydomain.com" target="_blank"&gt;www.mydomain.com&lt;/A&gt; hits the PIX I need it to go to server A.  When traffic for server.mydomain.com hits the PIX I need it to go to server B.&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 12:39:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/web-publishing-behind-501/m-p/965279#M938385</guid>
      <dc:creator>brownr0127</dc:creator>
      <dc:date>2019-03-11T12:39:08Z</dc:date>
    </item>
    <item>
      <title>Re: Web publishing behind 501</title>
      <link>https://community.cisco.com/t5/network-security/web-publishing-behind-501/m-p/965280#M938386</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;Unfortunatly an ASA/pix is not a reverse proxy box and does not have the ability to look into header information to do advanced decisions on http traffic routing.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The most you could hope for is to map those domain names to different public ip address's and then statically nat them through the pix to the private ip for that url.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 03 May 2008 00:15:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/web-publishing-behind-501/m-p/965280#M938386</guid>
      <dc:creator>Patrick Laidlaw</dc:creator>
      <dc:date>2008-05-03T00:15:35Z</dc:date>
    </item>
    <item>
      <title>Re: Web publishing behind 501</title>
      <link>https://community.cisco.com/t5/network-security/web-publishing-behind-501/m-p/965281#M938388</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I was afraid of that.  I wish we had the public IP's.  Can you recommend a Cisco product that might accomplish this along with being a firewall?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 03 May 2008 15:26:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/web-publishing-behind-501/m-p/965281#M938388</guid>
      <dc:creator>brownr0127</dc:creator>
      <dc:date>2008-05-03T15:26:29Z</dc:date>
    </item>
  </channel>
</rss>

