hmmm... i don't really think so... maybe I did not say it right in the first place. sorry...
I cannot tell what's the requested URI and what's the "desired" redirected URI from the original request.
Here how the dynamics are:
- the client does a request (HTTP or HTTPS) to lets say /index.jsp (i.e http://acme.com/index.jsp or https://acme.com/index.jsp)
- the app behind, makes a decision internaly where to send the client for its next request and sets the Location header as part of the redirect process (is not the LTM who does the redirection)
- the problem is that the app sends http://127.0.0.1/nexthop.jsp (could be http://127.0.0.1/any/other/path/hop.jsp as well) for the Location where the client needs to go next
- I need to intercept this Location header in the response from the app (it is just a portion of the total requests that are wrongly redirected by the app, not all - don't ask me, I haven't designed the app, I just need to provide the workaround until devs are getting their story straight) and change "http://127.0.0.1" with the original method and the original host name that the user requested in the first place, but to maintain the actual URI that is set by the app (as said, that is unknown to the LTM as it is built inside the app logic where the client is redirected after initial request). The final Location header send back to the client should be http://acme.com/nexthop.jsp or https://acme.com/nexthop.jsp or http://acme.com/any/other/path/hop.jsp or... I don't know what's it gonna be in the HTTP_REQUEST (the app logic is not at the LTM level)
Thanks,
Adrian