-
Notifications
You must be signed in to change notification settings - Fork 25.6k
SQL: the SSL default configuration shouldn't override the https protocol if used #34635
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
Conversation
|
Pinging @elastic/es-search-aggs |
costin
left a comment
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
matriv
left a comment
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. Left a comment.
| if (!isSSLPropertyPresent && !isSchemaPresent) { | ||
| enabled = StringUtils.parseBoolean(SSL_DEFAULT); | ||
| } else { | ||
| if (isSSLPropertyPresent && isHttpsScheme && !StringUtils.parseBoolean(settings.getProperty(SSL))) { |
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.
I think you can remove isSSLPropertyPresent here, it's always true as it's checked above.
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.
It's not necessarily always true @matriv. The first condition could be false if isSSLPropertyPresent is also false (but isSchemaPresent true). This check is on purpose set like this because I want the exception to be thrown only in that specific case.
…col if used (elastic#34635) * The default SSL option shouldn't override the https protocol if specified. Fixes elastic#33817
This fixes the bug reported in #33817.