You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I use the docker to start graphnode postgres and ipfs , I can find the GRAPH_GRAPHQL_MAX_DEPTH in Environment Variables, but I can not find Alias limit in GraphQL.
Maybe you can add the environment variable .
According to this blog https://checkmarx.com/blog/alias-and-directive-overloading-in-graphql/
When we talk about preventing DoS in GraphQL, we’re usually discussing how to handle complex queries with deeply nested or circular relationships or even about preventing batching attacks, but it’s not often that alias and directives are mentioned as potential vectors.
Are you aware of any blockers that must be resolved before implementing this feature? If so, which? Link to any relevant GitHub issues.
No response
Some information to help us out
Tick this box if you plan on implementing this feature yourself.
I have searched the issue tracker to make sure this issue is not a duplicate.
The text was updated successfully, but these errors were encountered:
Description
I use the docker to start graphnode postgres and ipfs , I can find the
GRAPH_GRAPHQL_MAX_DEPTH
in Environment Variables, but I can not find Alias limit in GraphQL.Maybe you can add the environment variable .
According to this blog https://checkmarx.com/blog/alias-and-directive-overloading-in-graphql/
When we talk about preventing DoS in GraphQL, we’re usually discussing how to handle complex queries with deeply nested or circular relationships or even about preventing batching attacks, but it’s not often that alias and directives are mentioned as potential vectors.
Are you aware of any blockers that must be resolved before implementing this feature? If so, which? Link to any relevant GitHub issues.
No response
Some information to help us out
The text was updated successfully, but these errors were encountered: