Netscaler Knowledgebase

While many people seem to like to use url rewrite I've never understood the fascination with it.  To me it is an outage call just waiting to happen.

The Oracle says it in the opening sentences of this thread "One of the most common mistakes by web designers ... to account for poor programming"

I've got close to 100 pairs of Load Balancers with over 12,000 different lb vserver's and over 50,000 real servers and not a single line of url rewriting.
Maybe I'm just lucky but I've always been able to convince the app teams to fix their code instead of having the Load Balancers do it for them.

Having spouted off how successful I've been... I'm now faced with a similar but different issue.  Security is mandating that applications be forbidden to return 4xx or 5xx error pages.  I'm being asked by several apps to fix the issue by trapping all 4xx and 5xx error responses and rewriting them to a 302 (and deleting the content of the earlier error message) to a standard error page.   Some of them want me to rewrite it to a 200 with the standard error message in it.

Any experience with this?  My take is to have the web server catch this with a standard error page but I may be loosing the battle after a successful run of many years...

What is the real hit to the Load Balancer with a Global policy like this?