Fix: Avoid sending query identifier to /jobs (when authenticated) #3831
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
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.
What type of PR is this? (check all applicable)
Description
The query identifier is sent over to
/jobsto correlate with query API keys (for public embeds and dashboards). However, when properly authenticated, there's no need to send that over.One consequence of sending over the superfluous argument in authenticated sessions is when editing queries, where
queryis the actual query text. When it gets added as a parameter to the/jobsendpoint, it could max out the URL size and error for large queries.Related Tickets & Documents
Mobile & Desktop Screenshots/Recordings (if there are UI changes)