Pass desired node in URL as query param

Your original iRule is simple enough, but I don't understand the intended traffic flow well enough to give you a specific answer.

 

 

I would start troubleshooting by applying your original iRule to a non-encrypted virtual server and sending to a non-encrypted node, with no ssl profiles applied to the virtual. You will have to ensure the default gateway is configured appropriately or add static routes supporting this outbound traffic, and you may also need to enable SNAT on the virtual if the return path from the server will not naturally traverse the LTM to reverse the destination address translation that happens by default.

 

 

Once you have that working, then you can move on to managing encrypted traffic, for which there are a few additional considerations: For HTTPS traffic, you can only see the request if you are decrypting @ LTM (clientSSL profile applied to the virtual server) and then if you want to send encrypted to the backend, you'd also apply a serverSSL profile.

 

 

A global rule that would handle both is possible, but how manageable it would be would depend on the of different conditions on which you'd need to direct traffic. I'd recommend creating a unique iRule for each virtual that includes only the relevant conditions.

 

 

HTH

 

/deb