-
Notifications
You must be signed in to change notification settings - Fork 295
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
Support client certificates for HTTP requests #767
Conversation
|
overall : looks ok. Did a brief review of the code. Please let's test this internally and merge. |
Current coverage is 75.70% (diff: 5.26%)@@ master #767 diff @@
==========================================
Files 223 223
Lines 8167 8151 -16
Methods 0 0
Messages 0 0
Branches 0 0
==========================================
+ Hits 6170 6171 +1
+ Misses 1997 1980 -17
Partials 0 0
|
I think for the sake of simplicity and clarity it is worth it. Also, if we change it before 1.0, we do not have to try to maintain the inconsistencies in the future.
There are a lot of things that are not documented in docs/Bots.md. I have now added all of the generic collectors along with their parameters. As I have mentioned before in #757, it would be nice to have a better solution to this. Also, I do not understand what exactly is meant by
Sorry, I hadn't noticed that. I changed it to
I just copied what was done before, but I agree and have now changed it.
Same, I just copied what was done before, but I changed it to ssl_client_cert |
This fixes #737
I also used this opportunity to consolidate the parameters that are supplied for HTTP requests and added the parameter parsing in the general CollectorBot.
There also seemed to be inconsistencies whether
http_ssl_proxy
orhttps_proxy
should be used. I replaced all of them withhttps_proxy
(seemed to be more common and documented).