http redirect with using different pools

Rewriting a URI would mean that LTM changes the requested host and/or URI before sending the request to the pool. The client would not see the change to the request as long as the application doesn't include the rewritten host and/or URI in response headers/content. For HTTP, the term redirecting the client denotes sending a 30x response with the Location header set to the new location. The client would see the change in host and/or URI. If the host was changed in a redirect, the client would resolve the new host value to an IP address and make a new HTTP request to that host.

 

 

Do you want the client to see the change in host and/or URI? Do the new host values resolve to the same virtual server as the original? The iRule example I posted rewrites the host and URI without redirecting the client. For a more expansive Apache ProxyPass iRule, you can check the Codeshare for two examples (Click here).

 

 

Aaron