Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upConsider supporting TLS renegotiation #1998
Comments
This comment has been minimized.
This comment has been minimized.
|
Looks like it should be in go 1.7 - golang/go#5742 |
This comment has been minimized.
This comment has been minimized.
|
Weve had a long discussion about this last night, I found and suggested the same and tried scraping the problematic URL with a go1.7 compiled prometheus server and got the same reponse |
grobie
added
help wanted
dependency/external
labels
Sep 16, 2016
brian-brazil
added
priority/Pmaybe
kind/enhancement
component/config
and removed
dependency/external
labels
Jul 14, 2017
brian-brazil
removed
the
help wanted
label
Jul 24, 2017
brian-brazil
changed the title
Problem with scraping metrics from HTTPS endpoint (TLS)
Consider supporting TLS renegotiation
Aug 2, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
vipetrul commentedSep 15, 2016
•
edited
It appears that when HTTPS endpoint has TLS renegotiation enabled, then Prometheus receives "local error: no renegotiation" error upon scraping.
It is OK if HTTPS endpoint is using TLS 1 protocol, as long as TLS renegotiation is disabled on the server.
Golang version. 1.6
No action is needed on this ticket, just wanted to report observed behavior.
Unfortunately underlying issue with TLS renegotiation was fixed, hence I cannot provide you with a link to a live example.