Application team asked us to do this because getting www.site.com instead of full URI is good for search engine crawlers and improves site search rankings. True or not we got a request and now need to implement it.
I see what you are saying about the redirect happening in the loop. That making it an interesting problem.
Clint requests www.site.com
Server response with www.site.com/home/default.htm
Client then requests www.site.com/home/default.htm
I need LTM to intercept www.site.com and send it to /home/default.htm on the background, but how do I prevent client from seeing /home/default.htm when server response back with the page?
Nimbostratus