feat: add query-gateway plugin for safe caching of read-only body queries - #13810
Open
fatihbm wants to merge 34 commits into
Open
feat: add query-gateway plugin for safe caching of read-only body queries#13810fatihbm wants to merge 34 commits into
fatihbm wants to merge 34 commits into
Conversation
fatihbm
marked this pull request as ready for review
August 12, 2026 15:03
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
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
Adds the
query-gatewayplugin, an opt-in cache boundary for read-only HTTP requests that carry query content in the request body.The plugin supports both client
POSTand RFC 10008QUERYrequests:POSTrequests are preserved when sent upstream.QUERYrequests are forwarded asPOSTby default for upstream compatibility.QUERYsupport can preserve theQUERYmethod.POSTandQUERYquery payloads produce the same canonical cache key.This is useful for search, analytics, reporting, Elasticsearch, and ClickHouse-style read-only requests. These workloads often use
POSTbecause they require a request body, even when their semantics are safe and idempotent. The plugin enables safe caching today without requiring immediate nativeQUERYsupport from every upstream.Which issue(s) this PR fixes:
Fixes #13807
Validation
POSTandQUERYscenarios, upstreamPOSTand nativeQUERYforwarding modes, and cache bypass cases.Checklist