<?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: https front end and http backend in Application Networking</title>
    <link>https://community.cisco.com/t5/application-networking/https-front-end-and-http-backend/m-p/845824#M16503</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;can you send me your email?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 15 Jan 2008 20:54:46 GMT</pubDate>
    <dc:creator>yycsandman007</dc:creator>
    <dc:date>2008-01-15T20:54:46Z</dc:date>
    <item>
      <title>https front end and http backend</title>
      <link>https://community.cisco.com/t5/application-networking/https-front-end-and-http-backend/m-p/845820#M16499</link>
      <description>&lt;P&gt;Hi there....I am having a small issue....I have a web app that is https based....I have installed the cert on the CSS, and DNS for this app points to the VIP....the client is wanting to have an https front end, and then load balance in http to the backend servers....the issue I am running into is that this only works if I have an active port 80 rule on that same VIP....if I suspend the port 80 rule and only leave the port 443 rule active on that VIP, it doesn't work....please see appropriate config portions below....Thanks in advance!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sandeep&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ANy suggestions?  I have been trying this for a couple of days now...it works fine if the backend sessions are also https, but the client has changed their requirement....&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ssl-proxy-list SSL1&lt;/P&gt;&lt;P&gt;  ssl-server 1&lt;/P&gt;&lt;P&gt;  ssl-server 1 rsakey app1-test&lt;/P&gt;&lt;P&gt;  ssl-server 1 rsacert app1-test&lt;/P&gt;&lt;P&gt;  ssl-server 1 vip address 10.19.55.10&lt;/P&gt;&lt;P&gt;  ssl-server 1 cipher rsa-with-rc4-128-md5 10.19.55.10 81&lt;/P&gt;&lt;P&gt;  backend-server 1&lt;/P&gt;&lt;P&gt;  backend-server 1 port 81&lt;/P&gt;&lt;P&gt;  backend-server 1 server-ip 10.19.55.132&lt;/P&gt;&lt;P&gt;  backend-server 1 ip address 10.19.55.132&lt;/P&gt;&lt;P&gt;  backend-server 2&lt;/P&gt;&lt;P&gt;  backend-server 2 port 81&lt;/P&gt;&lt;P&gt;  backend-server 2 server-ip 10.19.55.133&lt;/P&gt;&lt;P&gt;  backend-server 2 ip address 10.19.55.133&lt;/P&gt;&lt;P&gt;  backend-server 3&lt;/P&gt;&lt;P&gt;  backend-server 3 port 83&lt;/P&gt;&lt;P&gt;  backend-server 3 server-ip 10.19.55.132&lt;/P&gt;&lt;P&gt;  backend-server 3 ip address 10.19.55.132&lt;/P&gt;&lt;P&gt;  backend-server 4&lt;/P&gt;&lt;P&gt;  backend-server 4 port 83&lt;/P&gt;&lt;P&gt;  backend-server 4 server-ip 10.19.55.133&lt;/P&gt;&lt;P&gt;  backend-server 4 ip address 10.19.55.133&lt;/P&gt;&lt;P&gt;  backend-server 5&lt;/P&gt;&lt;P&gt;  backend-server 5 port 85&lt;/P&gt;&lt;P&gt;  backend-server 5 server-ip 10.19.55.132&lt;/P&gt;&lt;P&gt;  backend-server 5 ip address 10.19.55.132&lt;/P&gt;&lt;P&gt;  backend-server 6&lt;/P&gt;&lt;P&gt;  backend-server 6 port 85&lt;/P&gt;&lt;P&gt;  backend-server 6 server-ip 10.19.55.133&lt;/P&gt;&lt;P&gt;  backend-server 6 ip address 10.19.55.133&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;&lt;/P&gt;&lt;P&gt;service webserver002:81 &lt;/P&gt;&lt;P&gt;ip address 10.19.55.132 &lt;/P&gt;&lt;P&gt;port 81 &lt;/P&gt;&lt;P&gt;keepalive port 2199 &lt;/P&gt;&lt;P&gt;keepalive type tcp&lt;/P&gt;&lt;P&gt;protocol tcp &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;&lt;/P&gt;&lt;P&gt;service webserver003:81 &lt;/P&gt;&lt;P&gt;ip address 10.19.55.133 &lt;/P&gt;&lt;P&gt;port 81 &lt;/P&gt;&lt;P&gt;keepalive port 2199 &lt;/P&gt;&lt;P&gt;keepalive type tcp &lt;/P&gt;&lt;P&gt;protocol tcp &lt;/P&gt;&lt;P&gt;add ssl-proxy-list SSL1 &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; &lt;/P&gt;&lt;P&gt;service webserver002:83 &lt;/P&gt;&lt;P&gt;ip address 10.19.55.132 &lt;/P&gt;&lt;P&gt;port 83 &lt;/P&gt;&lt;P&gt;add ssl-proxy-list SSL1 &lt;/P&gt;&lt;P&gt;keepalive port 2399 &lt;/P&gt;&lt;P&gt;keepalive type tcp&lt;/P&gt;&lt;P&gt;protocol tcp &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;&lt;/P&gt;&lt;P&gt;service webserver003:83 &lt;/P&gt;&lt;P&gt;ip address 10.19.55.133 &lt;/P&gt;&lt;P&gt;port 83 &lt;/P&gt;&lt;P&gt;keepalive port 2399 &lt;/P&gt;&lt;P&gt;keepalive type tcp &lt;/P&gt;&lt;P&gt;protocol tcp &lt;/P&gt;&lt;P&gt;add ssl-proxy-list SSL1 &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;&lt;/P&gt;&lt;P&gt;service webserver002:85 &lt;/P&gt;&lt;P&gt;ip address 10.19.55.132 &lt;/P&gt;&lt;P&gt;port 85 &lt;/P&gt;&lt;P&gt;add ssl-proxy-list SSL1 &lt;/P&gt;&lt;P&gt;keepalive port 2599 &lt;/P&gt;&lt;P&gt;keepalive type tcp&lt;/P&gt;&lt;P&gt;protocol tcp &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;&lt;/P&gt;&lt;P&gt;service webserver003:85 &lt;/P&gt;&lt;P&gt;ip address 10.19.55.133 &lt;/P&gt;&lt;P&gt;port 85 &lt;/P&gt;&lt;P&gt;keepalive port 2599 &lt;/P&gt;&lt;P&gt;keepalive type tcp &lt;/P&gt;&lt;P&gt;protocol tcp &lt;/P&gt;&lt;P&gt;add ssl-proxy-list SSL1 &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;&lt;/P&gt;&lt;P&gt;service SSL_Front &lt;/P&gt;&lt;P&gt;slot 2 &lt;/P&gt;&lt;P&gt;type ssl-accel &lt;/P&gt;&lt;P&gt;keepalive type none &lt;/P&gt;&lt;P&gt;add ssl-proxy-list SSL1 &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;&lt;/P&gt;&lt;P&gt;owner app1-test &lt;/P&gt;&lt;P&gt; content app-test_back&lt;/P&gt;&lt;P&gt;    vip address 10.19.55.10&lt;/P&gt;&lt;P&gt;    add service webserver002:81&lt;/P&gt;&lt;P&gt;    add service webserver003:81&lt;/P&gt;&lt;P&gt;    add service webserver002:83&lt;/P&gt;&lt;P&gt;    add service webserver003:83&lt;/P&gt;&lt;P&gt;    add service webserver002:85&lt;/P&gt;&lt;P&gt;    add service webserver003:85&lt;/P&gt;&lt;P&gt;    balance aca&lt;/P&gt;&lt;P&gt;    protocol tcp&lt;/P&gt;&lt;P&gt;    port 81&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; &lt;/P&gt;&lt;P&gt;content app1-test_front &lt;/P&gt;&lt;P&gt;vip address 10.19.55.10&lt;/P&gt;&lt;P&gt;application ssl &lt;/P&gt;&lt;P&gt;add service SSL_Front &lt;/P&gt;&lt;P&gt;protocol tcp &lt;/P&gt;&lt;P&gt;port 443 &lt;/P&gt;&lt;P&gt;advanced-balance ssl &lt;/P&gt;&lt;P&gt;balance aca &lt;/P&gt;&lt;P&gt;active &lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 15 Jan 2008 16:28:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/https-front-end-and-http-backend/m-p/845820#M16499</guid>
      <dc:creator>yycsandman007</dc:creator>
      <dc:date>2008-01-15T16:28:37Z</dc:date>
    </item>
    <item>
      <title>Re: https front end and http backend</title>
      <link>https://community.cisco.com/t5/application-networking/https-front-end-and-http-backend/m-p/845821#M16500</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Well I find this a little confusing. First of all I see clear traffic on port 81 and not 80, and you have a content rule in port 81, so I guess that is what you mean.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now, it is expected that this will not work if you suspend the clear text rule since that this is the proper configuration.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You need to have the rule in port 443 to match traffic coming from the client and the clear text rule (port 81) to match traffic already decrypted coming from the SSL module&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 15 Jan 2008 20:15:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/https-front-end-and-http-backend/m-p/845821#M16500</guid>
      <dc:creator>Diego Vargas</dc:creator>
      <dc:date>2008-01-15T20:15:30Z</dc:date>
    </item>
    <item>
      <title>Re: https front end and http backend</title>
      <link>https://community.cisco.com/t5/application-networking/https-front-end-and-http-backend/m-p/845822#M16501</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for the quick reply....there is another port 80 rule setup for that vip....I was using that to test with the app until I got the front end https rules working....&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;my port 80 rules just says listen to 10.19.55.10 on port 80 and load balance btwn the webervers on port 8x in the back end...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am trying to do https front end and http backend....&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;no where in my SSL config have I configured port 80....but when I suspend that rule it all fails....&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am wondering if the backend server sessions are happening properly?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I don't fully get what you mean by "You need to have the rule in port 443 to match traffic coming from the client and the clear text rule (port 81) to match traffic already decrypted coming from the SSL module"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Haven'tI done that?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks again!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sandeep&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 15 Jan 2008 20:26:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/https-front-end-and-http-backend/m-p/845822#M16501</guid>
      <dc:creator>yycsandman007</dc:creator>
      <dc:date>2008-01-15T20:26:17Z</dc:date>
    </item>
    <item>
      <title>Re: https front end and http backend</title>
      <link>https://community.cisco.com/t5/application-networking/https-front-end-and-http-backend/m-p/845823#M16502</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Sandeep,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can I get the full config to see where is breaking out?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks!!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 15 Jan 2008 20:36:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/https-front-end-and-http-backend/m-p/845823#M16502</guid>
      <dc:creator>Diego Vargas</dc:creator>
      <dc:date>2008-01-15T20:36:49Z</dc:date>
    </item>
    <item>
      <title>Re: https front end and http backend</title>
      <link>https://community.cisco.com/t5/application-networking/https-front-end-and-http-backend/m-p/845824#M16503</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;can you send me your email?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 15 Jan 2008 20:54:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/https-front-end-and-http-backend/m-p/845824#M16503</guid>
      <dc:creator>yycsandman007</dc:creator>
      <dc:date>2008-01-15T20:54:46Z</dc:date>
    </item>
    <item>
      <title>Re: https front end and http backend</title>
      <link>https://community.cisco.com/t5/application-networking/https-front-end-and-http-backend/m-p/845825#M16504</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You can send it to &lt;A href="mailto:dmoravar@cisco.com"&gt;dmoravar@cisco.com&lt;/A&gt; or you can upload it here&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 15 Jan 2008 20:56:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/https-front-end-and-http-backend/m-p/845825#M16504</guid>
      <dc:creator>Diego Vargas</dc:creator>
      <dc:date>2008-01-15T20:56:45Z</dc:date>
    </item>
  </channel>
</rss>

