Assistance requested with HTTPS Response Redirect - VMware Platform Services Controller

Note: currently using a 45-day trial license with v11.6.1. When configuration is stable, it will eventually be moved to physical F5s running 12.1.0.

Another attempt did not produce any changes in the results. Used: https://support.f5.com/kb/en-us/products/big-ip_ltm/manuals/product/ltm-implementations-11-4-0/21.html Section: Creating a Rewrite profile to specify URI rules

Creating a Rewrite profile to specify URI rules

To configure the BIG-IP system to perform URI translation, you create a Rewrite profile, specifying one or more URI rules that associate a client-side path with a server-side URI. You also specify whether you want the URI translation to pertain to HTTP requests, responses, or both.

On the Main tab, click Local Traffic > Profiles > Services > Rewrite. The Rewrite profile list appears.
Click Create New Profile. The Create New Profile Rewrite popup screen appears.
In the Profile Name field, type a name, such as my_rewrite_profile.
From the Parent Profile list, select rewrite.
From the Rewrite Mode list, select URI Translation.
On the left pane, click URI Rules. An empty text box appears for displaying client-server URI mappings that you specify.
Click Add.
From the Rule Type list, select Both.
In the Client URI box, type a client path, such as /sales/.
In the Server URI box, type a server URI, such as http://appserver1.siterequest.com/sales/. You must include a scheme in the server URI that you specify. An example of a scheme is http.
Click OK. This displays a mapping of the specified client path to the associated server scheme, host, and path.
Click Add again.
From the Rule Type list, select Both.
In the Client URI box, type a client path, such as /marketing/.
In the Server URI box, type a server URI, such as http://appserver2.siterequest.com/marketing/. You must include a scheme in the server URI that you specify. An example of a scheme is http.
Click OK. This displays a mapping of the specified client path to the associated server scheme, host, and path.
Click OK.

The BIG-IP system now includes two URI rules for performing URI translation on both requests and responses. For example, the host name in a request destined for http://www.siterequest.com/sales/ will be translated to http://appserver1.siterequest.com/sales/, and the host name in a request destined for https://www.siterequest.com/marketing/ will be translated to http://appserver2.siterequest.com/marketing/. A reverse translation occurs on any response.

Again, this did not produce any changes in the results. Using the web browser to go to https://psc2.company.com still results in the web browser showing https://node1.company.com.

Thoughts?