Yeah, if you need to support lots of HTTP methods, you need to use Gateway mode.
In Gateway mode, you cannot re-write the URL. Whatever comes in goes out. Modifying the POST Request Target only works in Messaging mode:
solace1040(…est/rest-delivery-point/queue-binding)# post-request-target ?
COMMAND:
post-request-target
no post-request-target
DESCRIPTION:
The request-target string to use when sending requests. It identifies
the target resource on the far-end REST Consumer upon which to apply
the request. There are generally two common forms for the
request-target. The origin-form is most often used in practice and
contains the path and query components of the target URI. If the path
component is empty then the client must generally send a “/” as the
path. When making a request to a proxy, most often the absolute-form is
required. This configuration is only applicable when the Message VPN is <----
in REST messaging mode. <----
The no version of the command returns its value to the default (“”).
For your second, you want to configure the broker to send two GET requests to two different REST servers? From a single “incoming” GET? Essentially, pub/sub for REST? This would introduce a race condition, both backend servers would attempt to reply to the GET, and the broker will only return the first one that responds and discards the 2nd one. Is this the behaviour that you want? If not, can you more fully explain your desired setup and behaviour?