<?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 Hi Richard, in Application Networking</title>
    <link>https://community.cisco.com/t5/application-networking/ace-cookie-sticky-http-v-https/m-p/2780657#M42973</link>
    <description>&lt;P&gt;Hi Richard,&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Are you doing SSL offloading on ACE? If not, then ACE has no means to look into the HTTP header after redirection since it's encrypted and hence the problem. If you do have SSL offloading configured, then it should work fine.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Kanwal&lt;/P&gt;
&lt;P&gt;Note: Please mark answers if they are helpful.&lt;/P&gt;</description>
    <pubDate>Sun, 03 Jan 2016 19:35:51 GMT</pubDate>
    <dc:creator>Kanwaljeet Singh</dc:creator>
    <dc:date>2016-01-03T19:35:51Z</dc:date>
    <item>
      <title>ACE cookie sticky HTTP v HTTPS</title>
      <link>https://community.cisco.com/t5/application-networking/ace-cookie-sticky-http-v-https/m-p/2780656#M42972</link>
      <description>&lt;P&gt;I have 2 almost identical infrastructures in different data centres.&lt;/P&gt;
&lt;P&gt;In one, for a particular application I have HTTP and HTTPS connections allowed to the web server. On this site sitcky cookie sessions are working OK.&lt;/P&gt;
&lt;P&gt;In the other DC for the same application, we are redirecting HTTP requests to HTTPS. On this site sticky cookies sessions are not working.&lt;/P&gt;
&lt;P&gt;Do you need to do anything special if the flows are HTTPS ? I thought the sticky cookie session was just a function the ACE used to create the sticky session and was not really part of the flow as such.&lt;/P&gt;</description>
      <pubDate>Mon, 14 Dec 2015 09:12:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/ace-cookie-sticky-http-v-https/m-p/2780656#M42972</guid>
      <dc:creator>Richard Tapp</dc:creator>
      <dc:date>2015-12-14T09:12:15Z</dc:date>
    </item>
    <item>
      <title>Hi Richard,</title>
      <link>https://community.cisco.com/t5/application-networking/ace-cookie-sticky-http-v-https/m-p/2780657#M42973</link>
      <description>&lt;P&gt;Hi Richard,&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Are you doing SSL offloading on ACE? If not, then ACE has no means to look into the HTTP header after redirection since it's encrypted and hence the problem. If you do have SSL offloading configured, then it should work fine.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Kanwal&lt;/P&gt;
&lt;P&gt;Note: Please mark answers if they are helpful.&lt;/P&gt;</description>
      <pubDate>Sun, 03 Jan 2016 19:35:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/ace-cookie-sticky-http-v-https/m-p/2780657#M42973</guid>
      <dc:creator>Kanwaljeet Singh</dc:creator>
      <dc:date>2016-01-03T19:35:51Z</dc:date>
    </item>
  </channel>
</rss>

