Re: how do you use the host eg. host.domain.com

p.mckay · ‎06-21-2005

I need to create a content rule and to handle various host headers. I see there is a HTTP header field. I see examples on the site with user-agent. I need to be able to create content rules that handle things like promo.domain.com. I already have dql’s that handle numerous redirects to the www.brand.com. The dql’s handle lot’s of variations on the root domain spelling and other registered names related to the brand. Web and Marketing groups now want to campaign on promo.brand.com. I believe there will be a custom service to handle this on the server.

I just need some example of how the host can be used in the configuration.

Gilles Dufour · ‎06-22-2005

first, let me say you need to have your dns correctly setup to link the new domain name to a VIP address that exist on the CSS.

If this ip address is only being used by this new domain name, you don't need to play with DQL.

If the ip is shared by several domain, and if you need to direct the traffic to different server, this is when you need DQL.

You could also use the command 'url "//promo.brand.com/*'.

I'm not sure what information you need exactly from your message.

If you could rephrase and let us know exactly what you need we can assist more.

Regards,

Gilles.

p.mckay · ‎06-22-2005

Thanks for the responce:

I hope this not to long and draw out but...

The web/marketing group has ask me to setup a configuration where they can use promo.brand.com. Currently there is an existing site www.brand.com with some large dql’s in place. I have included and example from the current configuration. There will be a DNS A record for promo in the brand.com zone that points to the same ip address used by the current brand.com vip also. When the url promo.brand.com comes through the css I need to be able to have a content rule handle this. From the documentation I have seen I was leaning towards the host. I did not know you could just use the full uri for this.

I think that I will be creating a new service or two services such as

service SERVER01_PROMO_1234

port 1234

ip address 10.1.1.1

keepalive type tcp

service SERVER02_PROMO_1234

port 1234

ip address 10.1.1.2

keepalive type tcp

But for the content rule I need to handle promo.brand.com

I was unaware that the url could be as simple as //promo.brand.com/* if this is all it is then great. I am interested though finding examples that reference how to handle host headers.

So on experimenting

CSS11503# sh run owner PMCK

!*************************** OWNER ***************************

owner PMCK

content hostheader

vip address 192.168.x.x1 <-- Same as existing

protocol tcp

port 80

url "//promo.brand.com/*"

add service SERVER01_PROMO_1234

add service SERVER02_PROMO_1234

Currently I have something like this

service SERVER01_BRAND _1234

port 1234

ip address 10.1.1.1

keepalive type tcp

active

service SERVER02_BRAND _1234

port 1234

ip address 10.1.1.2

keepalive type tcp

active

dql BRAND_DQL

domain brandvaration.com

domain www. brandvaration.com

domain brandvaration.ca

domain www. brandvaration.ca

domain brandvaration.co.uk

domain www. brandvaration.co.uk

domain brandvarationxxx.ca

domain www. brandvarationxxx.ca

Owner Someone

content BRANDAPP_80

vip address 192.168.x.x1

port 80

protocol tcp

url "/*" eql app_content

add service SERVER01_BRAND_1234

add service SERVER02_BRAND_1234

advanced-balance arrowpoint-cookie

active

content BRANDWEB_80

protocol tcp

port 80

url "/*"

add service WEBSERVER04_BRAND_8300

vip address 192.168.x.x1

add service WEBSERVER03_BRAND_8300

active

content BRAND_EXTRANET_80

add service SERVER02_BRAND_8300

advanced-balance arrowpoint-cookie

vip address 192.168.x.x1

protocol tcp

port 80

url "/extranet/*"

active

content BRAND_FTP_80

protocol tcp

port 80

url "/ftp/*"

add service SERVER02_BRAND_8300

advanced-balance arrowpoint-cookie

vip address 192.168.x.x1

active

content BRAND_REDIRECT

url "/*" dql BRAND_DQL

vip address 192.168.x.x1

add service BRAND_REDIRECT_SVC

protocol tcp

port 80

active

Gilles Dufour · ‎06-24-2005

I think this should work.

If not, you could use another DQL for your new domain name and use it with 'url "/*" dql ...' as you already did.

Regards,

Gilles.