Sterling Secure Proxy on Red Hat Linux version 2.6.32-696.1.1.el6.
x86_64 is unable to route to different Outbound Nodes based on the URL that is sent to the proxy.
Example (test vs prod at end of url):
Incoming URL https:proxy.com:443/rosettanet/test
--> we want to route to test-server.com:49073/rosettanet
Incoming URL https:proxy.com:443/rosettanet/prod
--> we want to route to prod-server.com:49073/rosettanet
Note that the trading partner is sending from the same server hostname/IP for both Test and Prod.
This should be a basic feature of any proxy solution, especially Sterling Secure Proxy. If we would have known of this limitation we would have chosen to use BlueCoat proxy as our solution instead of SSP.