Feature Request: matching in Application hostnames

I ran across this limitation when implementing WebAccelerator at my company, and wanted to document it here for posterity, in hopes that the developers might consider an enhancement in a future release.

 

 

In our environment, we are running a single VS with multiple applications/policies/pools. We have separated things this way by design. We use HTTP classes with different hostnames to map the traffic back to specific pools.

 

So the flow goes roughly:

 

VS -> HTTP Class A -> App A -> Policy A -> HTTP Class A -> Pool A

 

VS -> HTTP Class B -> App B -> Policy B -> HTTP Class B -> Pool B

 

VS -> HTTP Class C -> App C -> Policy C -> HTTP Class C -> Pool C

 

and so on..

 

The issue we ran into was because we use sub-domains for different territories. For example:

 

for application A we have a list of hostnames like:

 

appA.us.domain.com

 

appA.uk.domain.com

 

appA.ca.domain.com

 

...etc.

 

On the HTTP Class we can easily specify 'appA.*.domain.com' and match all territories. Now, when we pass it off to the WA, we have to map it again to App A using the hostname. But the application's 'Requested Host' field does not allow for the same wildcard mapping: you can only use a wildcard on the 'first part' of the hostname. So as a result, we have to specify EVERY full hostname here. We cannot simply use '*.domain.com', because this cannot be mapped to more than one application. If the application let us use the same wildcard mapping as the HTTP class, we'd be done. Or even if it would let you match on the tail end like: 'appA*' that would work.

 

 

Please consider this in a future release and make the 'Requested Host' matching in the Application more flexible!

 

 

Thanks.