Current Limitation
The custom HTTP headers sent by the Webhook provider are not being propagated to the subscriber’s callback URL.
As per current implementation, these headers are dropped during message forwarding. The expected behaviour is that any custom headers received by the Webhook receiver from the provider should be preserved and forwarded as part of the outgoing HTTP request to the subscriber.
Suggested Improvement
Implement a mechanism in the Webhook delivery flow to retain and propagate headers from the provider to the subscriber.
Version
4.2.0