Ok… if you use the Gateway mode, the URL is passed through exactly as is … you can’t rewrite it . That is only possible with REST Messaging mode. In Gateway, if you just want the URL to remain the same, then that’s what it does… the broker acts as a proxy.
So if you want to do some target rewriting, you’ll want to use Messaging mode, have 2 RDPs, and then inside your two RDPs’ queue bindings you can configure a custom target. Your first queue would be listening to hr/> and your second RDP queue would be listening to payrole/> . Then each inside the queue binding of each RDP you could specify your custom path for the downstream REST server.
And remember that your REST publisher will need to insert that header that I was talking about : Solace-Reply-To-Destination in order for the backend response to get routed back to the publisher.
Take a look at this video I made which shows some of what I’m talking about substitution expressions for the downstream target: https://youtu.be/INMrSL2fA3E?t=439 (don’t worry that the video is for S3, doesn’t really matter).