<?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 ACE - Sticky using XFF client value in Application Networking</title>
    <link>https://community.cisco.com/t5/application-networking/ace-sticky-using-xff-client-value/m-p/2604788#M42553</link>
    <description>&lt;P&gt;Might be a stupid question&amp;nbsp; ....but we have a situation where client traffic is LB to our proxy infrastructure , at the LB the XFF client&amp;nbsp;address&amp;nbsp;is inserted into the header and source sticky is enabled. We now need to LB to addtional servers( more than within our proxy infrastructure) downstream from our proxy servers&amp;nbsp;and retain the client sessions, if we use source sticky we will have a one to one relationship with the downstream servers . This we don't want as we want to spread the load across all downstream servers. My question is instead of source IP sticky could we use say the XFF info or something else to stick sessions to the downstream servers.&lt;/P&gt;</description>
    <pubDate>Tue, 21 Oct 2014 11:16:02 GMT</pubDate>
    <dc:creator>wriddiford</dc:creator>
    <dc:date>2014-10-21T11:16:02Z</dc:date>
    <item>
      <title>ACE - Sticky using XFF client value</title>
      <link>https://community.cisco.com/t5/application-networking/ace-sticky-using-xff-client-value/m-p/2604788#M42553</link>
      <description>&lt;P&gt;Might be a stupid question&amp;nbsp; ....but we have a situation where client traffic is LB to our proxy infrastructure , at the LB the XFF client&amp;nbsp;address&amp;nbsp;is inserted into the header and source sticky is enabled. We now need to LB to addtional servers( more than within our proxy infrastructure) downstream from our proxy servers&amp;nbsp;and retain the client sessions, if we use source sticky we will have a one to one relationship with the downstream servers . This we don't want as we want to spread the load across all downstream servers. My question is instead of source IP sticky could we use say the XFF info or something else to stick sessions to the downstream servers.&lt;/P&gt;</description>
      <pubDate>Tue, 21 Oct 2014 11:16:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/ace-sticky-using-xff-client-value/m-p/2604788#M42553</guid>
      <dc:creator>wriddiford</dc:creator>
      <dc:date>2014-10-21T11:16:02Z</dc:date>
    </item>
    <item>
      <title>Hi,So your proxy server will</title>
      <link>https://community.cisco.com/t5/application-networking/ace-sticky-using-xff-client-value/m-p/2604789#M42554</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;So your proxy server will need to contact different servers through loadbalancer?&lt;/P&gt;&lt;P&gt;You can use cookies for the same and make the ACE to insert cookie. I haven't tried using XFF header and value for sticky but ACE let's you configure it so it can be tried too.&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>Tue, 21 Oct 2014 14:54:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/ace-sticky-using-xff-client-value/m-p/2604789#M42554</guid>
      <dc:creator>Kanwaljeet Singh</dc:creator>
      <dc:date>2014-10-21T14:54:11Z</dc:date>
    </item>
    <item>
      <title>Cheers for that ......looks</title>
      <link>https://community.cisco.com/t5/application-networking/ace-sticky-using-xff-client-value/m-p/2604790#M42555</link>
      <description>&lt;P&gt;Cheers for that ......looks like we need to play a bit&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 21 Oct 2014 15:17:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/ace-sticky-using-xff-client-value/m-p/2604790#M42555</guid>
      <dc:creator>wriddiford</dc:creator>
      <dc:date>2014-10-21T15:17:22Z</dc:date>
    </item>
  </channel>
</rss>

