Add mod_ssl-like Placeholder Support for Server and Client Certificates in Caddy #6780
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.
This pull request introduces functionality similar to Apache's mod_ssl by adding support for dynamic placeholders for server and client certificates in Caddy. The implementation addresses the following:
1)Dynamic Placeholder Population:
Populates placeholders for both server and client certificates during TLS connections, enabling detailed certificate information to be accessed in configurations (e.g., headers, logs).
2)Support for Default Values:
Ensures placeholders return meaningful default values (e.g., null or descriptive strings) when client certificates are not provided (e.g., in non-mTLS scenarios).
3)Centralized Logic:
Introduced a new function, handleMTLSEnabledWithExport, to handle placeholder population efficiently, reducing redundancy and improving maintainability.