<?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 Redirect port 80 to port 443 in Application Networking</title>
    <link>https://community.cisco.com/t5/application-networking/redirect-port-80-to-port-443/m-p/51580#M561</link>
    <description>&lt;P&gt;We are using Novell's iChain services for authentication of remote users.  We need resilience and the CSS11051 was recommended by Cisco using WebNS4.01.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The user after presenting  their  digital cerficate, will get redirected from port 80 to port 443.  Another requirement is that there be stickiness configured based on the SSL session ID.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Has anyone done this configuration before and gotten it to work correctly.&lt;/P&gt;</description>
    <pubDate>Thu, 26 Sep 2002 06:03:10 GMT</pubDate>
    <dc:creator>abarnard</dc:creator>
    <dc:date>2002-09-26T06:03:10Z</dc:date>
    <item>
      <title>Redirect port 80 to port 443</title>
      <link>https://community.cisco.com/t5/application-networking/redirect-port-80-to-port-443/m-p/51580#M561</link>
      <description>&lt;P&gt;We are using Novell's iChain services for authentication of remote users.  We need resilience and the CSS11051 was recommended by Cisco using WebNS4.01.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The user after presenting  their  digital cerficate, will get redirected from port 80 to port 443.  Another requirement is that there be stickiness configured based on the SSL session ID.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Has anyone done this configuration before and gotten it to work correctly.&lt;/P&gt;</description>
      <pubDate>Thu, 26 Sep 2002 06:03:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/redirect-port-80-to-port-443/m-p/51580#M561</guid>
      <dc:creator>abarnard</dc:creator>
      <dc:date>2002-09-26T06:03:10Z</dc:date>
    </item>
    <item>
      <title>Re: Redirect port 80 to port 443</title>
      <link>https://community.cisco.com/t5/application-networking/redirect-port-80-to-port-443/m-p/51581#M562</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You can provide resilience a number of ways with the CSS products and this enables it to provide many solutions - although you should look at using a later version of code than 4.01 - Check CCO for latest.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The CSS can stick on SSL session id, but this is not really practical in the real world due to an issue with Microsift explorer, where it renegotiates the SSL session id every few minutes. (Netscape is fine). So unless you can guarantee that you user base will run only Netscape browsers &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt; , SSL sticky will not work. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A preferred method is to incorporate an SSL offload device into the design - this enables several benefits:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Offload SSL processing from your servers&lt;/P&gt;&lt;P&gt;Provide SSL redundancy (several SSL offload devices can be used in a cluster)&lt;/P&gt;&lt;P&gt;Provide sticky for SSL - this is because the SSL session is terminated on the SSL device and then passed back to the real server as cleartext, so you can now stick  based on a whole range of attributes - URL, cookie etc.&lt;/P&gt;&lt;P&gt;To work effectively, this needs to be incorporated into your content switch design.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Darren.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 30 Sep 2002 20:54:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/redirect-port-80-to-port-443/m-p/51581#M562</guid>
      <dc:creator>darren.page</dc:creator>
      <dc:date>2002-09-30T20:54:56Z</dc:date>
    </item>
    <item>
      <title>Re: Redirect port 80 to port 443</title>
      <link>https://community.cisco.com/t5/application-networking/redirect-port-80-to-port-443/m-p/51582#M563</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks Darren,  I will test your suggestion.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 01 Oct 2002 05:39:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/redirect-port-80-to-port-443/m-p/51582#M563</guid>
      <dc:creator>abarnard</dc:creator>
      <dc:date>2002-10-01T05:39:42Z</dc:date>
    </item>
  </channel>
</rss>

