fix: move Gemini API key from URL query param to request header#75
Merged
iam-vipin merged 1 commit intoRocketChat:mainfrom Mar 24, 2026
Merged
Conversation
- Move API key from URL query parameter to x-goog-api-key header to prevent key exposure in server logs, browser history, and network traces
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description
The Gemini API key was being passed as a URL query parameter (
?key=...). This is a security vulnerability that exposes the key in:This PR moves the API key to the
x-goog-api-keyHTTP request header, which is the recommended authentication method by Google.References