04-07-2005 01:26 AM
HI,
I've to do loadbalancing based on parts of the URL.
The URL will look like this:
www.myserver.com/a/b/c/d/x=12345/bdc/*.htm
If the x=<digits> is includes I've to use server1-3 1 if the x is not included I've to use server 4-6
I can right now think of two (2) methods:
1) url ="/x=*"
2) using a header-field group with field "request-line" and the operator contains.
Now my two questions:
- Is it enough to define in method 1 only "/x=*" or do I have to write down the whole path (/a/b/c/d/x=*) or is it possible to do url="*/x=*".
- Is there any other way to have this sort balancing done?
- Which method is best practise?
Thanks in advance for answering.
Kind Regards,
Joerg
04-07-2005 01:56 AM
Joerg,
1.you will need to specify the full path up to x=.
2.can't think of any other solution
3.no particular recommendation
Gilles.
04-07-2005 02:09 AM
Hi Gilles,
thanks for your reply.
So both methods are possible. From my point of view method two is more flexible even if less specific. Is there any other draw back you can think of using method two, the one with the header group.
Kind regards,
Joerg
04-21-2005 09:32 AM
We are using Header Field Groups and have not run into any unusual problems. It seems to work flawlessly.
We are using the "request-line contain" method to key off a certain word. Then if that word doesn't exist, it just defaults to the regular HTTP content rule.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide