-
Notifications
You must be signed in to change notification settings - Fork 37
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.
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
InfluxDbHttpSender encodes auth string with newline symbol in the end #80
Comments
Could you give an example of you config with |
Sure
UPD. latest version of library, dropwizard 1.2.0 |
I have the same issue. I am using the influxdb docker without any configuration. I basically call the reporter like this : new InfluxDbHttpSender(influxUrl.getProtocol(),
influxUrl.getHost(),
influxUrl.getPort(),
db, influxUrl.getUserInfo(), TimeUnit.SECONDS,
1000, 1000, "") and influxUrl is then I get the error : api-service_1 | 13:47:37.650 [metrics-influxDb-reporter-1-thread-1] WARN com.izettle.metrics.influxdb.InfluxDbReporter - Unable to report to InfluxDB with error 'Illegal character(s) in message header value: Basic cm9vdDpyb290
api-service_1 | 13:48:37.643 [metrics-influxDb-reporter-1-thread-1] WARN com.izettle.metrics.influxdb.InfluxDbReporter - Unable to report to InfluxDB with error 'Illegal character(s) in message header value: Basic cm9vdDpyb290 I'm using the 1.2.2 version. |
I think I have the fix, I try a PR soon. Found from stackoverflow |
what I did was extending
|
How can you extend as the properties are private final? |
I found the reason of this bug : I was using another dependency that requires commons-condecs at version 1.4, and this version... adds a @rickard-von-essen-iz To ensure my fix, I have a unittest, do you want me to make a PR for that? |
I'm trying to add authorization to my http(s) reporter, so I set config entry to
auth: user:password
.Later, here it gets encrypted to
dXNlcjpwYXNzd29yZA==\r\n
-note the newline symbols in the end. And then during connection construction, it fails withIllegal character(s) in message header field
here .Full stack trace:
Sample config
Is there any way to make this working?
The text was updated successfully, but these errors were encountered: