<?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: Web Servers with Certificate in Application Networking</title>
    <link>https://community.cisco.com/t5/application-networking/web-servers-with-certificate/m-p/1123059#M23091</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You have two options&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. (As you mentioned) Donot offload ssl on CSS and send the traffic to Server directly for ssl offload. Shortcoming of this method is that you cannot use HTTP headers for making Intelligent LB decisions&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You simply need a content rule listening on TCP 443. For e.g&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;content apps-443&lt;/P&gt;&lt;P&gt;    add service svc1&lt;/P&gt;&lt;P&gt;    add service svc2&lt;/P&gt;&lt;P&gt;    vip address 192.168.1.1&lt;/P&gt;&lt;P&gt;    protocol tcp&lt;/P&gt;&lt;P&gt;    port 443&lt;/P&gt;&lt;P&gt;    active&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;service svc1&lt;/P&gt;&lt;P&gt;  ip address 10.10.10.1&lt;/P&gt;&lt;P&gt;  port 443&lt;/P&gt;&lt;P&gt;  protocol tcp&lt;/P&gt;&lt;P&gt;  keepalive type tcp&lt;/P&gt;&lt;P&gt;  keepalive port 443&lt;/P&gt;&lt;P&gt;  active&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;service svc2&lt;/P&gt;&lt;P&gt;  ip address 10.10.10.2&lt;/P&gt;&lt;P&gt;  port 443&lt;/P&gt;&lt;P&gt;  protocol tcp&lt;/P&gt;&lt;P&gt;  keepalive type tcp&lt;/P&gt;&lt;P&gt;  keepalive port 443&lt;/P&gt;&lt;P&gt;  active&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2. Do end2end SSL. Where you will have to install cert on CSS, offload ssl on css, make LB decision based on Layer7 headers, encrypt the http request again and send it to the server as  encrypted request (Server will do the SSL offloading again). &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH &lt;/P&gt;&lt;P&gt;Syed Iftekhar Ahmed&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 21 Oct 2008 17:43:49 GMT</pubDate>
    <dc:creator>Syed Iftekhar Ahmed</dc:creator>
    <dc:date>2008-10-21T17:43:49Z</dc:date>
    <item>
      <title>Web Servers with Certificate</title>
      <link>https://community.cisco.com/t5/application-networking/web-servers-with-certificate/m-p/1123058#M23090</link>
      <description>&lt;P&gt;We have 11503-SSL in one-arm mode and have requirement that the Certifiates be on the Web Servers. Can I just not do ssl acceleration on the CSS and pass 443 to the Web Servers. What would that config look like?&lt;/P&gt;&lt;P&gt;Thank You&lt;/P&gt;&lt;P&gt;Matt&lt;/P&gt;</description>
      <pubDate>Tue, 21 Oct 2008 15:32:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/web-servers-with-certificate/m-p/1123058#M23090</guid>
      <dc:creator>matt.s</dc:creator>
      <dc:date>2008-10-21T15:32:11Z</dc:date>
    </item>
    <item>
      <title>Re: Web Servers with Certificate</title>
      <link>https://community.cisco.com/t5/application-networking/web-servers-with-certificate/m-p/1123059#M23091</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You have two options&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. (As you mentioned) Donot offload ssl on CSS and send the traffic to Server directly for ssl offload. Shortcoming of this method is that you cannot use HTTP headers for making Intelligent LB decisions&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You simply need a content rule listening on TCP 443. For e.g&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;content apps-443&lt;/P&gt;&lt;P&gt;    add service svc1&lt;/P&gt;&lt;P&gt;    add service svc2&lt;/P&gt;&lt;P&gt;    vip address 192.168.1.1&lt;/P&gt;&lt;P&gt;    protocol tcp&lt;/P&gt;&lt;P&gt;    port 443&lt;/P&gt;&lt;P&gt;    active&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;service svc1&lt;/P&gt;&lt;P&gt;  ip address 10.10.10.1&lt;/P&gt;&lt;P&gt;  port 443&lt;/P&gt;&lt;P&gt;  protocol tcp&lt;/P&gt;&lt;P&gt;  keepalive type tcp&lt;/P&gt;&lt;P&gt;  keepalive port 443&lt;/P&gt;&lt;P&gt;  active&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;service svc2&lt;/P&gt;&lt;P&gt;  ip address 10.10.10.2&lt;/P&gt;&lt;P&gt;  port 443&lt;/P&gt;&lt;P&gt;  protocol tcp&lt;/P&gt;&lt;P&gt;  keepalive type tcp&lt;/P&gt;&lt;P&gt;  keepalive port 443&lt;/P&gt;&lt;P&gt;  active&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2. Do end2end SSL. Where you will have to install cert on CSS, offload ssl on css, make LB decision based on Layer7 headers, encrypt the http request again and send it to the server as  encrypted request (Server will do the SSL offloading again). &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH &lt;/P&gt;&lt;P&gt;Syed Iftekhar Ahmed&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 21 Oct 2008 17:43:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/web-servers-with-certificate/m-p/1123059#M23091</guid>
      <dc:creator>Syed Iftekhar Ahmed</dc:creator>
      <dc:date>2008-10-21T17:43:49Z</dc:date>
    </item>
  </channel>
</rss>

