CSS content configuration problem

Question

Hello,
I've a strange problem with CSS configuration (written below). In 10% of times, content "ABCD80old2" doesn't work - clients trying to access "/AB*" resources, receive answers from Serv3 and Serv4 (not from Serv1 or Serv2, as they should). Upgrade to the version 8.2.01 didn't resolve the problem.
Here's the configuration from CSS 11506:
content ABCD80old2
vip address 10.30.4.254
advanced-balance sticky-srcip
sticky-inact-timeout 120
add service Serv1
add service Serv2
port 80
protocol tcp
url "/AB*"
active
content ABCD80
vip address 10.30.4.254
protocol tcp
port 80
advanced-balance sticky-srcip
sticky-inact-timeout 120
add service Serv3
add service Serv4
active
Thank you in advance for any ideas.

Answer 1

I have to configure different content for URL /AB*, because such resources reside on different servers. So, if clients are incorrectly redirected to Serv3 or Serv4, they get "Page not found".
Configuration for services:
service Serv1
ip address 10.30.2.22
protocol tcp
port 80
keepalive type tcp
keepalive tcp-close fin
keepalive frequency 20
active
service Serv2
ip address 10.30.2.23
protocol tcp
port 80
keepalive type tcp
keepalive tcp-close fin
keepalive frequency 20
active
service Serv3
ip address 10.30.2.24
port 80
keepalive type tcp
protocol tcp
active
service Serv4
ip address 10.30.2.25
port 80
keepalive type tcp
protocol tcp
active
Correct me, if I'm wrong, but I read, that CSS looks for the most _exact_ content first - so URL with /AB* should be processed with content ABCD80old2, which is more precise than content ABCD80.