backend/http: add ca_file support for custom CA trust #38024
+244
−11
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.
Summary
Add support for configuring a custom CA certificate bundle for the HTTP backend using a new
ca_fileoption (andTF_HTTP_CA_FILE).This allows TLS certificate verification with private or internal CAs without disabling verification.
Fixes #36937
Changes
ca_file/TF_HTTP_CA_FILEbackend optionTarget Release
1.15.x
Changes to Security Controls
Yes. This change improves TLS security by allowing users to configure a trusted CA bundle for the HTTP backend. This enables proper server certificate verification in environments that use private or internal certificate authorities, reducing the need to disable TLS verification via
skip_cert_verification.No existing security controls are removed or weakened.
CHANGELOG entry