| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
Use the Data Collection outgoing response body decision when attaching GraphQL execution results. Preserve the sendDefaultPii and maxRequestBodySize gate when Data Collection is absent. Co-Authored-By: Claude <noreply@anthropic.com>
|
Sorry, something went wrong.
📲 Install BuildsAndroid
|
Sorry, something went wrong.
Performance metrics 🚀
|
Sorry, something went wrong.
Bring the queue option removal and preceding stack updates into this layer.
There was a problem hiding this comment.
LGTM 👍
Sorry, something went wrong.
…ata-collection-outgoing-response-body
Semver Impact of This PR🟡 Minor (new features) 📋 Changelog PreviewThis is how your changes will appear in the changelog. This PR will not appear in the changelog. 🤖 This preview updates automatically when you update the PR. |
Sorry, something went wrong.
…ata-collection-outgoing-response-body
…ata-collection-outgoing-response-body
…ata-collection-outgoing-response-body
…ata-collection-outgoing-response-body
| Back | FazBrowse Home | New Git URL |
PR Stack (Data Collection)
📜 Description
Apply the outgoing response body policy to GraphQL Java execution results attached by ExceptionReporter.
Explicit Data Collection controls the serialized GraphQL response independently from the request document. When Data Collection is absent, the existing sendDefaultPii and maxRequestBodySize gate remains unchanged.
💡 Motivation and Context
A server-side GraphQL execution result is outgoing response body content and can contain customer data. It requires a directional policy distinct from the incoming GraphQL document and variables.
Refs #5666
💚 How did you test it?
📝 Checklist
🔮 Next steps
Apply request and response header collection behavior across HTTP integrations.
#skip-changelog