Hi All
I had an issue with ACE 2 year before where..sending all youtube traffic to same cache while using URL hash. I had below response from Cisco TAC..
Any1 knows if the new image resolved this...?
Regarding your question about the used predictor and "splitting" the requests going to youtube to be handled by two caches, please note that the URL hashing will hash the domain name up to the "?" only, so we unfortunately cannot distinguish the caches to which to send the request when using this predictor method. The "?" is the default URL parsing delimiter.
Therefore, what we could try is changing the predictor method to another type, for example hash destination|source address or round robin to verify if the loads gets distributed among the caches more evenly.
There, we can see that you can specify a begin- and end-pattern to look
for a specific pattern within an URL, too, however, as already stated,
the hashing has no effect after the "?".
Regards
Sameer Shah
