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

Ability to add additional information in HTTP header #1768

Closed
ramakrishnachirra opened this issue May 30, 2016 · 2 comments
Closed

Ability to add additional information in HTTP header #1768

ramakrishnachirra opened this issue May 30, 2016 · 2 comments
Labels
enhancement libbeat

Comments

@ramakrishnachirra
Copy link

ramakrishnachirra commented May 30, 2016 •
edited

Hi,
Currently there is no way of adding an additional information in HTTP header (for authentication on server) in http request from filebeat to ElasticSearch. Please add this as a new feature in future releases of FileBeat. This would be very helpful for authentication purposes.

Thanks,
RK
@ruflin
Copy link
Member

ruflin commented May 30, 2016

Can you add some more details about the headers you would like to add (with an example if possible)? I assume you are not referring to http auth? https://github.com/elastic/beats/blob/master/libbeat/_beat/config.full.yml#L86

@ramakrishnachirra
Copy link
Author

ramakrishnachirra commented May 30, 2016 •
edited

Hi Ruflin,
Thanks for your quick reply.
We have a requirement where we need to have a custom header in HTTP call which may contain Key-Value pair(eg: device MAC ID), and may be used on the reverse proxy server for validation .After a successful validation, the reverse proxy would forward it to the ElasticSearch. This is someway of custom authentication which we are looking at.

Thanks,
RK

@tsg tsg mentioned this issue Jan 18, 2017
Merged
tsg pushed a commit to tsg/beats that referenced this issue Jan 24, 2017
Custom HTTP headers for the Elasticsearch output
2073858 
Configuration looks like this:

```
output.elasticsearch.headers:
  X-My-Header: Contents of the header
```

To use from the CLI:

```
metricbeat -E "output.elasticsearch.headers.X-test=Test value"
```

It's not possible to set the same header name more than once with different values,
but it is possible to separate header values with a comma, which has the same meaning
as per the RFC.

Closes elastic#1768.
monicasarbu pushed a commit that referenced this issue Jan 25, 2017
@tsg @monicasarbu
Custom HTTP headers for the Elasticsearch output (#3400)
b04384a 
Configuration looks like this:

```
output.elasticsearch.headers:
  X-My-Header: Contents of the header
```

To use from the CLI:

```
metricbeat -E "output.elasticsearch.headers.X-test=Test value"
```

It's not possible to set the same header name more than once with different values,
but it is possible to separate header values with a comma, which has the same meaning
as per the RFC.

Closes #1768.
@markwalkom markwalkom mentioned this issue Apr 21, 2019
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement libbeat
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ruflin @ramakrishnachirra