-
Notifications
You must be signed in to change notification settings - Fork 209
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
KREST-7955 421 misdirected request if host does not match SNI #410
KREST-7955 421 misdirected request if host does not match SNI #410
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm. I like the parameterized tests for mTLS enablement.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@trnguyencflt Thinking more on it, it requires more work to be ready. This new feature should have "config" that acts as a feature-flag to safely roll this out. But agree with the change so far 👍
This will be done on the subsequent cc-spec change (when http2 enable -> enable sni check) (https://confluentinc.atlassian.net/browse/KREST-11523) For this PR, it is complete on its own because we have a configuration to switch it on/off. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
…vletContextHandler
This PR adds SniHandler that checks for SNI against the host of the request, if they don't match, response with 421.
This handler is controlled by configuration to turn off/on, default is disabled.
sni.check.enabled
Jira ticket