Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

HTTP Output Plugin does not honor custom Host header #5803

Closed
niftyhoot opened this issue May 5, 2019 · 1 comment · Fixed by #5810
Closed

HTTP Output Plugin does not honor custom Host header #5803

niftyhoot opened this issue May 5, 2019 · 1 comment · Fixed by #5810
Labels
bug unexpected problem or unintended behavior
Milestone
1.10.4

Comments

@niftyhoot
Copy link

Relevant telegraf.conf:

[[outputs.http]]
  url = "http://192.168.2.53/collector"
  [outputs.http.headers]
    Host = "ingest.example.com"
    Hostess = "ingest.example.com"

System info:

Steps to reproduce:

  1. Define custom http headers as shown above
  2. Check tcpdump output

Expected behavior:

The custom string of Host header should have been used while sending the POST requests out.

Actual behavior:

The "Host" header remains the 192.168.2.53. The other header "Hostess" for example, gets properly updated.

Additional info:
@glinton glinton added the bug unexpected problem or unintended behavior label May 6, 2019
@glinton
Copy link
Contributor

glinton commented May 6, 2019

Go discussion here - golang/go#7682

@glinton glinton mentioned this issue May 6, 2019
Merged
@glinton glinton added this to the 1.10.4 milestone May 6, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug unexpected problem or unintended behavior
Projects
None yet
Milestone
1.10.4
Development

Successfully merging a pull request may close this issue.

Set host header if configured on http output influxdata/telegraf
2 participants
@glinton @niftyhoot