iRule re-write to replace ISAPI re-write

I think a switch statement is most efficient up to a point (50 - 100 entries?). Beyond that, your idea for classes would probably be more efficient. I don't think either option would add significant latency though.

 

 

Do you always want to rewrite the paths regardless of which host header value the request was made with? If so, it would be relatively simple to have one host class and one path class. If you only want to rewrite the path if a specific host is requested, then you could create a class with the "source" and "destination" host and path values, like www.external-host.example.com/external/path/ www.inside-host.example.com/internal/path/.

 

 

You might try either using the ProxyPass rule (Click here) or adapting some of the logic from it.

 

 

Aaron