<?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: CSM-S SSL multi-domain certs in Application Networking</title>
    <link>https://community.cisco.com/t5/application-networking/csm-s-ssl-multi-domain-certs/m-p/729495#M13952</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;you can have multiple certs but they need to be assigned to different vserver.&lt;/P&gt;&lt;P&gt;So, you need to be able to distinguish between the 2 at TCP/IP level.&lt;/P&gt;&lt;P&gt;Either by ip address or by tcp port.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ie: test.com will be on x.x.x.x:443&lt;/P&gt;&lt;P&gt;    test.uk  will be on x.x.x.x:444&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;or&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;    test.com will be on x.x.x.x:443&lt;/P&gt;&lt;P&gt;    test.uk  will be on y.y.y.y:443&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is true for any loadbalancer.&lt;/P&gt;&lt;P&gt;Since you need to know which cert to use decrypt the traffic and only when the traffic is decrypted can you see the http header that contains the hostname.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Gilles.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 18 Jun 2007 13:29:12 GMT</pubDate>
    <dc:creator>Gilles Dufour</dc:creator>
    <dc:date>2007-06-18T13:29:12Z</dc:date>
    <item>
      <title>CSM-S SSL multi-domain certs</title>
      <link>https://community.cisco.com/t5/application-networking/csm-s-ssl-multi-domain-certs/m-p/729494#M13951</link>
      <description>&lt;P&gt;Has anyone implemented multi-domain SSL certs on the CSM-S?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;i.e. 1 SSL cert contains test.com &amp;amp; test.uk&lt;/P&gt;</description>
      <pubDate>Mon, 18 Jun 2007 08:43:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/csm-s-ssl-multi-domain-certs/m-p/729494#M13951</guid>
      <dc:creator>dhinshelwood</dc:creator>
      <dc:date>2007-06-18T08:43:40Z</dc:date>
    </item>
    <item>
      <title>Re: CSM-S SSL multi-domain certs</title>
      <link>https://community.cisco.com/t5/application-networking/csm-s-ssl-multi-domain-certs/m-p/729495#M13952</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;you can have multiple certs but they need to be assigned to different vserver.&lt;/P&gt;&lt;P&gt;So, you need to be able to distinguish between the 2 at TCP/IP level.&lt;/P&gt;&lt;P&gt;Either by ip address or by tcp port.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ie: test.com will be on x.x.x.x:443&lt;/P&gt;&lt;P&gt;    test.uk  will be on x.x.x.x:444&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;or&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;    test.com will be on x.x.x.x:443&lt;/P&gt;&lt;P&gt;    test.uk  will be on y.y.y.y:443&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is true for any loadbalancer.&lt;/P&gt;&lt;P&gt;Since you need to know which cert to use decrypt the traffic and only when the traffic is decrypted can you see the http header that contains the hostname.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Gilles.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 18 Jun 2007 13:29:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/csm-s-ssl-multi-domain-certs/m-p/729495#M13952</guid>
      <dc:creator>Gilles Dufour</dc:creator>
      <dc:date>2007-06-18T13:29:12Z</dc:date>
    </item>
  </channel>
</rss>

