I lost some time investigating why Heartbeat 6.6.2 (lastest stable) was not respecting the "Host" http header I was configuring in an HTTP monitor.
I was using exactly what the doc was saying, etc.
Turns out when I understood the issue was specific to a specific header.. "Host" and not to all http headers. I looked for a known or unknown bug and found:
If this fix is not scheduled to be backported to older heartbeat, I would recommend a documentation fix for older version that support the http header settings but ignore the specific "Host" http header.
What do you think, poor me (and others) trying to only override the Host header and not knowing about this bug in heartbeat < 7.
I am now using heartbeat 7.0.0-beta1 because I absolutely needed this fix for what I'm doing.
So I was very happy to found that by moving to a pre-release I'm unblocked for this, but wanted to save the headache to others through a doc update.
With the check.request.headers doc.
Gold license customer
Running self-managed 5.5.2 cluster on AWS ECS.