CSS and stickieness

[olge]

Hi,

I have two following content rules pointing to the same vip and port, but one of them is sticky on a specific URL.

For some reason the sticky part does not work. The question is, can you have two such rules together?

content web1

add service service1

add service service2

url "/*"

protocol tcp

port 81

vip address 10.6.229.16

active

content web1_Reporting

add service service1

add service service2

protocol tcp

port 81

url "/web/reporting/*"

advanced-balance sticky-srcip

vip address 10.6.229.16

active

Thanks

[bhooker]

I would think that the content rules are parsed in order. I'd try removing content web1 and adding it in again after web1_Reporting. that gives you an if/then/else type of logic in your configuration.

[Gilles Dufour]

like a list of static routes, the order has nothing to do here. The CSS selects the best match (longest match).

Gilles.

[Gilles Dufour]

could you send us a sniffer trace showing the problem ?

Stickyness will work only if the request start with /web/reporting/

Any other url will match the other content rule.

So, even if the first request is a match for rule web1_reporting, if the next request inside the same tcp connection does not match that rule, the css will reloadbalance the connection.

Gilles.

[olge]

Gilles, you could be right on the money.

I will check to see if this could be the issue.

Alec

[olge]

Gilles,

You were right. There was a call outside "/web/reporting/*" thus load balancing to a different web server.

Is there anyway to combine two urls into one sticky session for example

url1: "/web/reporting1/*"

url2: "/web/reporting2/*"

Thanks again,

Alec

[bhooker]

have a look at configuring a urql

http://www.cisco.com/en/US/products/hw/contnetw/ps792/products_configuration_guide_chapter09186a008015774e.html#wp1047892

[olge]

Brian,

URQL works if you have specific file names. I actually need to have a "*" (wildcard) and URQL does not support that.

Thanks,

Alec

[Gilles Dufour]

you could do

url "/web/reporting*"

or create 2 content rules with the same services and use arrowpoint-cookie instead of sticky source-ip.

Gilles.