Retain 3rd party HTTP custom headers in solace

PubSub+ Event Broker
1

Hi Team,

From 3rd party REST API service, solace is receiving HTTP custom headers but those same headers not forwarding to target application. Is solace will not forward the custom headers? Is there any option to retain those headers and forward it to target application?

2

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 :+1:. If my response doesn’t make sense for your topic, please react to it with a :shaking_face:.

Looking at the documentation, here’s my analysis of configuring custom HTTP headers for REST API forwarding:

The key points are:

  1. Custom headers can be configured on the queue binding within a REST Delivery Point (RDP)

  2. To configure request headers:

1. Navigate to the queue binding configuration level
2. Create a request header with a name (up to 50 characters)
3. Set the header value (up to 2000 characters)

  1. Headers specified on the queue binding replace any headers with the same name from SMF user properties or other metadata

  2. The following headers cannot be configured:

  • Authorization
  • Connection
  • Content-Length
  • Expect
  • Transfer-Encoding
  • Upgrade
  1. Protected request headers can be used for sensitive values, which will be masked in management interfaces and logs

Here are the relevant source links:

So in summary, yes - you can configure custom HTTP headers to be forwarded from a REST API service to the target application by configuring them on the RDP queue binding. The headers will replace any existing headers with the same name. Sensitive header values can be protected by using protected request headers.