when I use solace RDP to forward message, seems RDP override the original request header, how to maintain the original message request headers same as sending from rest producer.
eg. if the rest producer send a message to the queue binding in RDP with request header mykey:myvalue, and value is runtime dynamic value. we except the request header mykey:myvalue can be forward to the consumer endpoint. how can i may this kind setup in the solace RDP.
Hi there, I’m Solly AI, I generate responses to your questions using the power of the Solace Agent Mesh:
Please remember that AI technology can make mistakes so ensure that you read our Disclaimer.
AI Generated responses are a work in progress, your help in evaluating my response would be awesome! If my response makes sense, please mark it as a solution or give a 
. If my response doesn’t make sense for your topic, please react to it with a 
.
Let me analyze the question about configuring RDP to maintain and forward original message request headers.
Looking through the documentation, there is no direct mention of a specific configuration to maintain and forward original message request headers from REST producers to consumer endpoints. However, there are a few relevant points to consider:
The documentation mentions that RDPs can be configured with request headers at the queue binding level, but these are for adding new headers rather than forwarding existing ones.
There is a “Transparent” authentication scheme mentioned that specifically deals with authorization headers, which “passes along existing authorization header metadata instead of discarding it.”
The documentation notes that headers specified on queue bindings replace all headers of the same name from SMF user properties or generated from other metadata.
Given this information, I cannot provide a definitive answer about how to maintain and forward all original request headers. The documentation suggests that some headers may be preserved or replaced depending on the configuration, but does not explicitly state how to preserve all original headers.
For the most accurate information, you may want to check these relevant sources:
According to Solace REST HTTP Message Encoding
So depends on which REST mode your broker message VPN is configured with. If it is REST messaging mode, the headers may get dropped. If it is Microgateway mode, it headers will be maintained.
A Sample echo test in microgateway mode shows the header is sent to the REST endpoint and return to the requester:
