if the URL contains the components in the second column below, the URL up to and including the 2nd column’s keyword gets rewritten to be the third column. So
and then it gets shipped out of the apache server’s LAN interface where it travels to the Oracle apps tier. The connection to the web browser stays open, and when the response returns from the apps it is rewritten back to what it was and shipped back to the browser, then the connection to the browser is closed.
As long as you are having the BIG-IP do the SSL termination for your backend servers, then there shouldn’t be a problem. the protocol portion of the URL isn’t passed as part of the HTTP request, it is determined by how the web servers is configured on the given port.
For the response, it’s just string replacement, so there shouldn’t be a problem. BTW, for the response, you could probably get away with using a Stream profile and a simple string replacement. Since it is a basic string map on the response (“http://new.web.com:10125” to “https://old.abc.com”) you could specify those values in your stream profile parameter.
As Joe mentioned, once the SSL has been decrypted on LTM, you can issue a redirect to http or https the same way, regardless of whether the clientside connection was over SSL or clear. This example would redirect all requests to the URL listed:
when HTTP_REQUEST {
Send a 302 redirect to the client
HTTP::redirect "http://www.example.com/new_uri.html"
}