Please see each section for in-depth documentation
This section describes the configuration options for GraphQL Protect.
Protect supports various running modes for different needs and purposes.
serveruns as an HTTP proxy protection your GraphQL during runtime. Check out the Deployment Options section for more configuration optionsvalidateruns as a CLI tool, validating your Persisted Operations against your schema and configured protections.versionoutputs versioning info of protect
This section contains all the documentation about each protection feature.
- Persisted Operations
- Block Field Suggestions
- Max Aliases
- Max Tokens
- Enforce POST
- Max Batch
- Access Logging
This section contains in depth documentation for run strategies
GraphQL Protect makes use of gqlparser to parse and validate GraphQL schemas & GraphQL requests. Gqlparser's spec support is and select portions of the Draft. gqlparser uses graphql-js as a reference implementation, resulting a similar level of graphql spec support.
If experience any issues related to spec support, or you want to verify the (draft spec) feature you want to use is supported, it's best to inspect the gqlparser library directly for your use case.
Currently, handling encoded responses from the upstream is not supported, we're open for contributions : )