Add ability to disable SNI host validation #3659
Merged
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.
Proposed changes
Problem: HTTP/2 clients can encounter 421 Misdirected Request errors when redirecting between subdomains using wildcard certificates due to connection reuse with mismatched SNI and Host headers.
Solution: Add disableSNIHostValidation field to NginxProxy CRD that conditionally removes the SNI Host validation logic, allowing mismatching host connection reuse with documented security trade-offs per GEP-3567.
Testing: Verified using openssl s_client with mismatched SNI (foo.example.com) and Host header (bar.example.com) - returns 421 when flag is set to false (default), 200 when flag is set to true.
Closes #3226
Checklist
Before creating a PR, run through this checklist and mark each as complete.
Release notes
If this PR introduces a change that affects users and needs to be mentioned in the release notes,
please add a brief note that summarizes the change.