CSS content configuration problem

Unanswered Question
May 8th, 2007

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.

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
vadi_ag Wed, 05/09/2007 - 06:01

Kindly help me understand why u have added this url "/AB*" in content ABCD80old2 i see a problem here cos the content ABCD80 looks for protocol tcp port 80 only and where as

content ABCD80old2 looks for port 80

protocol tcp url "/AB*" this cud be the reason for this issue to solve this u can add add service Serv1 add service Serv2 in

content ABCD80 and try this works out

Vadi

marta.sokolowska Fri, 05/11/2007 - 02:33

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.

stephen.evans Wed, 05/30/2007 - 07:31

We also have a very similar problem, we are using two servers and two content Content Rules. About two or three times a day URL requests that match content rule 1 which should go to server 1 actually go though to server 2 causing HTTP errors such as 404 etc. Is this a know bug? any help would be much appriciated.

Stephen

Actions

This Discussion