Steps to reproduce:
List the minimal actions needed to reproduce the behavior.
- Create an influx client with custom httpClient which has some "default" headers set.
- Get for example a writeApi instance, and send some points with DEBUG mode enabled.
- We dont see the custom added headers being sent to influx when looking at influx client logfile.
Expected behavior:
We should see the custom headers being sent to influx host.
To add some context I have influx API under cloudflare zero trust. I want to use service tokens to allow influx client to connect to and write points to my influx API. AFAIK this is not possible ATM due to this headers issue.
Actual behavior:
Headers are I guess overwritten when calling the "send" request from http client, more details: https://docs.guzzlephp.org/en/7.0/request-options.html?highlight=default%20header#headers
Specifications:
- Client Version: Guzzle 7
- InfluxDB Version: latest
- Platform: linux (debian)
Steps to reproduce:
List the minimal actions needed to reproduce the behavior.
Expected behavior:
We should see the custom headers being sent to influx host.
To add some context I have influx API under cloudflare zero trust. I want to use service tokens to allow influx client to connect to and write points to my influx API. AFAIK this is not possible ATM due to this headers issue.
Actual behavior:
Headers are I guess overwritten when calling the "send" request from http client, more details: https://docs.guzzlephp.org/en/7.0/request-options.html?highlight=default%20header#headers
Specifications: