<?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 PIX - Cut-Through Proxy via HTTPS in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/pix-cut-through-proxy-via-https/m-p/455204#M533632</link>
    <description>&lt;P&gt;Sorry for that long introduction&lt;/P&gt;&lt;P&gt;================================&lt;/P&gt;&lt;P&gt;When we use SSL (AAA Secure-HTTP-CLIENT)in order to authenticate, the PIX send to the Browser a HTML form asking the userid-password. The HTML source code built and sent by the PIX indicate that the form will be send to a site using protocol HTTPS against an IP address. EX: &lt;A class="jive-link-custom" href="https://" target="_blank"&gt;https://&lt;/A&gt;(ip address of the web site).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Having that kind of URL asking for the protocol HTTPS and specifying an IP address instead of a site name is not conform to the SSL protocol and make the certificate (sent by the PIX to the browser) generate a browser alert saying that the site doesn't match. CN field in the certificate which represent the name of the site can not match an IP address.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So question is : is there a way PIX will send that form (asking the user and pswd) with the &lt;A class="jive-link-custom" href="HTTPS://" target="_blank"&gt;HTTPS://&lt;/A&gt;(name of the site) instead of the IP address.   &lt;/P&gt;</description>
    <pubDate>Fri, 21 Feb 2020 08:22:13 GMT</pubDate>
    <dc:creator>robetrem</dc:creator>
    <dc:date>2020-02-21T08:22:13Z</dc:date>
    <item>
      <title>PIX - Cut-Through Proxy via HTTPS</title>
      <link>https://community.cisco.com/t5/network-security/pix-cut-through-proxy-via-https/m-p/455204#M533632</link>
      <description>&lt;P&gt;Sorry for that long introduction&lt;/P&gt;&lt;P&gt;================================&lt;/P&gt;&lt;P&gt;When we use SSL (AAA Secure-HTTP-CLIENT)in order to authenticate, the PIX send to the Browser a HTML form asking the userid-password. The HTML source code built and sent by the PIX indicate that the form will be send to a site using protocol HTTPS against an IP address. EX: &lt;A class="jive-link-custom" href="https://" target="_blank"&gt;https://&lt;/A&gt;(ip address of the web site).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Having that kind of URL asking for the protocol HTTPS and specifying an IP address instead of a site name is not conform to the SSL protocol and make the certificate (sent by the PIX to the browser) generate a browser alert saying that the site doesn't match. CN field in the certificate which represent the name of the site can not match an IP address.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So question is : is there a way PIX will send that form (asking the user and pswd) with the &lt;A class="jive-link-custom" href="HTTPS://" target="_blank"&gt;HTTPS://&lt;/A&gt;(name of the site) instead of the IP address.   &lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 08:22:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-cut-through-proxy-via-https/m-p/455204#M533632</guid>
      <dc:creator>robetrem</dc:creator>
      <dc:date>2020-02-21T08:22:13Z</dc:date>
    </item>
    <item>
      <title>Re: PIX - Cut-Through Proxy via HTTPS</title>
      <link>https://community.cisco.com/t5/network-security/pix-cut-through-proxy-via-https/m-p/455205#M533634</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;As far as I know, you cannot change the way it works with this IP address.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 08 Sep 2005 17:45:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-cut-through-proxy-via-https/m-p/455205#M533634</guid>
      <dc:creator>umedryk</dc:creator>
      <dc:date>2005-09-08T17:45:09Z</dc:date>
    </item>
  </channel>
</rss>

