ref(http): Don't send X-ClickHouse-Key header when no password is configured #5857
+16
−9
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Just adding some context - 400's don't happen in ClickHouse 22.8, so this is just affecting self-hosted folks (who should be able to upgrade soon) but yeah - |
MeredithAnya
approved these changes
May 3, 2024
untitaker
approved these changes
May 6, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Overview
When a user has no password configured, sending a request with empty
X-ClickHouse-Keyheader causes a 400.Maybe the
clickhouse_passwordfield should have been anOption<&str>instead of a&str, in case people have an empty password configured, but I would like this to be fixed now.