# Heartbeat bug with fix in 7.x, if no backport... doc fix in 6.x?

**URL:** <https://discuss.elastic.co/t/heartbeat-bug-with-fix-in-7-x-if-no-backport-doc-fix-in-6-x/172377>\
**Category:** Beats\
**Tags:** heartbeat\
**Created:** [March 14, 2019, 4:01pm UTC](https://discuss.elastic.co/t/heartbeat-bug-with-fix-in-7-x-if-no-backport-doc-fix-in-6-x/172377 "2019-03-14T16:01:00Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![martinr\_ubi](https://avatars.discourse-cdn.com/v4/letter/m/b5e925/32.png) [@martinr\_ubi](https://discuss.elastic.co/u/martinr_ubi)\
**Post date:** [March 14, 2019, 4:01pm UTC](https://discuss.elastic.co/t/heartbeat-bug-with-fix-in-7-x-if-no-backport-doc-fix-in-6-x/172377/1 "2019-03-14T16:01:00Z")

</div>

Hi,

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:

> <https://github.com/elastic/beats/issues/9376>

Question is:  
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.

It would go here I guess:  
[https://www.elastic.co/guide/en/beats/heartbeat/current/configuration-heartbeat-options.html#monitor-http-check](https://www.elastic.co/guide/en/beats/heartbeat/current/configuration-heartbeat-options.html#monitor-http-check)

With the check.request.headers doc.

Martin  
Gold license customer  
Running self-managed 5.5.2 cluster on AWS ECS.

---

<div class="post-metadata">

**Author:** ![Andrew\_Cholakian1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrew_cholakian1/32/3612_2.png) [@Andrew\_Cholakian1](https://discuss.elastic.co/u/Andrew_Cholakian1)\
**Post date:** [March 14, 2019, 4:40pm UTC](https://discuss.elastic.co/t/heartbeat-bug-with-fix-in-7-x-if-no-backport-doc-fix-in-6-x/172377/2 "2019-03-14T16:40:06Z")

</div>

The fix targeted 6.7 [https://github.com/elastic/beats/pull/9728](https://github.com/elastic/beats/pull/9728) . 6.7 should be released relatively soon and should include this patch except in the very unlikely event that something goes terribly wrong.

---

<div class="post-metadata">

**Author:** ![martinr\_ubi](https://avatars.discourse-cdn.com/v4/letter/m/b5e925/32.png) [@martinr\_ubi](https://discuss.elastic.co/u/martinr_ubi)\
**Post date:** [March 14, 2019, 4:47pm UTC](https://discuss.elastic.co/t/heartbeat-bug-with-fix-in-7-x-if-no-backport-doc-fix-in-6-x/172377/3 "2019-03-14T16:47:45Z")

</div>

Sorry for missing this and wasting _your_ time...

Martin

---

<div class="post-metadata">

**Author:** ![Andrew\_Cholakian1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrew_cholakian1/32/3612_2.png) [@Andrew\_Cholakian1](https://discuss.elastic.co/u/Andrew_Cholakian1)\
**Post date:** [March 14, 2019, 4:52pm UTC](https://discuss.elastic.co/t/heartbeat-bug-with-fix-in-7-x-if-no-backport-doc-fix-in-6-x/172377/4 "2019-03-14T16:52:45Z")

</div>

No worries at all! It was confusing given the age of the patch.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [April 11, 2019, 4:56pm UTC](https://discuss.elastic.co/t/heartbeat-bug-with-fix-in-7-x-if-no-backport-doc-fix-in-6-x/172377/5 "2019-04-11T16:56:31Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.