The refactor had unintended side-effects: when selecting a certificate the NameToCertificate map which is built using this call ensured that more specific certificates are preferred over wildcard matches. We rely on that behaviour to present the correct certificate to clients.
This reverts commit 6c6bd520ad939910fe8c0830558f6dd179e7d113.
Resolves: cloudfoundry/routing-release#401
A short explanation of the proposed change:
An explanation of the use cases your change solves
Instructions to functionally test the behavior change using operator interfaces (BOSH manifest, logs, curl, and metrics)
Expected result after the change
Current result before the change
Links to any other associated PRs
[ ] I have viewed signed and have submitted the Contributor License Agreement
[ ] I have made this pull request to the main branch
The refactor had unintended side-effects: when selecting a certificate the NameToCertificate map which is built using this call ensured that more specific certificates are preferred over wildcard matches. We rely on that behaviour to present the correct certificate to clients.
This reverts commit 6c6bd520ad939910fe8c0830558f6dd179e7d113.
Resolves: cloudfoundry/routing-release#401
A short explanation of the proposed change:
An explanation of the use cases your change solves
Instructions to functionally test the behavior change using operator interfaces (BOSH manifest, logs, curl, and metrics)
Expected result after the change
Current result before the change
Links to any other associated PRs
[ ] I have viewed signed and have submitted the Contributor License Agreement
[ ] I have made this pull request to the
mainbranch[ ] I have run all the unit tests.
[ ] (Optional) I have run Routing Acceptance Tests and Routing Smoke Tests
[ ] (Optional) I have run CF Acceptance Tests