Suraj Nath

@Jakob3xD checking in on this PR, we would be open to merge this if you can update and rebase it.

@Jakob3xD following up on this, I am open to merge this if this can be rebased and updated to include changes from master. 🙏🏼

For usecases like these, we recommend [building](https://github.com/prometheus/blackbox_exporter#building-the-software) the binaries yourself. If you manage to get it working, please feel free to upstream the changes. I would be happy to review...

> HTTP request still uses the Transfer-Encoding: chunked header and ignores the user-specified Content-Length. not sure if I understand the issue here, seems like expected behaviour. I am reading more...

I think it would be a breaking change to change metric names underneath users. if we do this, it should be done in a opt-in style where users who wish...

not sure if I understand the use-case here, please share more details to better understand the use-case.

Hi, our release pipeline was broken, and team is working on a fix. we should have the binaries built and pushed once that's sorted out.

Hi, this is out of scope for the blackbox exporter, this project focuses on endpoint probing. Please use a traceroute exporter such as [jefsg/traceroute-exporter](https://github.com/jefsg/traceroute-exporter) or [akarneliuk/prometheus-traceroute-exporter](https://github.com/akarneliuk/prometheus-traceroute-exporter). Also, please don't tag...

~Hi 👋🏼, coming from the cleanup 🧹~ ~This PR is quite old and there's https://github.com/prometheus/blackbox_exporter/pull/613 looks to be superset of this PR.~ ~I am going to close this, please feel...

oops, meant to close the [PR](https://github.com/prometheus/blackbox_exporter/pull/358). reopening this issue.