How to prevent default header parameter from being passed with webhook action in Watcher

Elastic Stack Elasticsearch
,
1

I have a Watcher watch that uses webhook action to send HTTPS request to a Mule API. It looks like this:
</>
”webhook”: {
”scheme”: “XXXX“
”host”: “XXXXX“
”port”: 443
”method”: “post“
”path”: “xxx/yyy/zzz”
”params”: {},
”headers”: {
“client-id”: “XXXXXXXXXXXXX“
“client-secret”: “XXXXXXXXXX“
“Content-Type”: “application/json“
}
”body”: {XXXXXXX}
}
</>

The HTTP response I’m receiving from the Mule API is:
HTTP 403 , invalid header parameter ‘accept-charset‘

I have not set this header in my request. Is this a default header being added? How do I avoid sending it as part of webhook action execution?

2

It looks like that header is set here, and that there is no way to avoid it unfortunately. Is there no way to configure the Mule API to ignore it (I am not familiar with that API at all)?

3

Hi Keith. Thanks for linking the java source file. I’m checking with the team that owns the Mule API to know if they can accept that header.
Can only ‘password‘ fields in watcher be redacted? I would like the client-secret associated with the API to not be visible in plaintext in the Painless script. Can that be done?

4

There are a few headers that are redacted as well (X-Elastic-App-Auth and Authorization), but unfortunately it’s not customizable.