cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
553
Views
0
Helpful
3
Replies

http header load balancing and dql lists.

rich.polyak
Level 1
Level 1

Can I utilize http header load balancing and dql's? If I match part of the http header, and then match the dql would this work and allow me to send traffice as defined below?

For example, if I have

header-field-group www1

header-field urlString request-line contain "www1"

header-field-group www2

header-field urlString request-line contain "www2"

dql list_domain

domain test.com

domain test1.com

domain test2.com

and content rules

owner test

content rule www

vip address 192.168.128.151

protocol tcp

port 80

url "/*" dql list_domain

add service server1

add service server2

active

content rule www1

vip address 192.168.128.151

protocol tcp

port 80

url "/*" dql list_domain

add service server1

header-field-rule www1

active

content rule www2

vip address 192.168.128.151

protocol tcp

port 80

url "/*" dql list_domain

add service server2

header-field-rule www2

active

3 Replies 3

pgolding
Level 1
Level 1

Rich,

This is a legal config but it may not achieve what you require. If www1 is only within test1.com and www2 is only within test2.com, there is no need to specify both the host name and domain name. Either dql or header field alone may do what you want.

To comment further, we would need to understand what you are trying to achieve.

Peter

Thx for the reply. What the web developers are trying to accomplish is this. All www1 traffic goto webserver1 all www2 traffic goto webserver2 and so on and so on. and all other traffic balanced between all the servers.

Currently I'm using dql's for all the different domains, but you can't utilize wild cards in dql's.

On your production site we have like 10 to 15 sites on 1 vip address, but on service end we are doing port mapping, 80, 81, 82, 83, 84 and so on to differentiate the differnt web sites.

On the Vip side I utilize dql's so that I can map it to the port mapping on the back end.

I was readding about the http header and thought that utilize this to match the first part of the url, www, www1, www2, and so on, and the rest of the domain on the back end I could cut down on the dql lists by 2 thirds?

This way I have just a dql for the last 2 thirds of the domain? and the http header for the 1st part?

Rich,

If each site has a unique FQDN, then just DQL will do the job. For example -

dql a

domain a.com

dql b

domain b.com

etc

content a.com

vip, protocol, port, add service for "a" site

url "/*" dql a

content b.com

same vip etc as above

url "/*" dql b

Do this for each site, then end with a rule with no dql to catch all the other non specific sites.

I think that will cover what you are after.

Peter

Review Cisco Networking for a $25 gift card