Cisco ACE: http-header based Stickiness

Unanswered Question
Sep 15th, 2008

Hi All,

I'm trying to configure a sticky policy to make HTTP sessions from Mobile Users to stick to the WAP Server they were served before. The IP-addressing based sticky policy is not ideal as the Mobile Users can roam around and use a different IP-Address.

So I configured the following http-header based sticky policy:

sticky http-header x-up-subno TD_Testing

timeout 2

replicate sticky

serverfarm TD_WWW

where x-up-subno is an HTTP header field containing Users' MSISDN, for example:

x-up-subno: MN002138210335\r\n

My question is if I apply the above stikcy policy to a policy-map would ACE loadbalance based on the header value? that is MSISDN, and NOT based on the header name itself.

My fear is that all the HTTP traffic will get diverted to a single WAP server as all of it will have that HTTP header.

Thanks!

- Kashif

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Syed Iftekhar Ahmed Mon, 09/15/2008 - 10:40

Stickiness will be based on Header-value.

Header based functionality is similar to cookie based persistence.

Header-Name/Cookie-name tells ACE to look for that particular Header-field/Cookie-Name and then Stickiness is based on the Header/cookie value.

Syed Iftekhar Ahmed

Syed Iftekhar Ahmed

kasiddiq Mon, 09/15/2008 - 11:09

Thanks Iftekhar. I will test this in the lab and find out if it works.

Regards,

- Kashif

Actions

This Discussion