Cherry-pick #22190 to 7.x: [Heartbeat] Add tls fields when connecting through proxy #22881
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Cherry-pick of PR #22190 to 7.x branch. Original message:
What does this PR do?
This updates Heartbeat to enrich an event with TLS information when the connection has been established via an HTTP proxy.
Why is it important?
Because tls fields are missing from events when an HTTPS connection is performed through a proxy.
Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.How to test this PR locally
Tested with tinyproxy (HTTP) and stunnel+tinyproxy (HTTPS)
Related issues
Closes #15797