You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Andreas Schaefer (Jira)" <ji...@apache.org> on 2023/03/28 16:00:00 UTC

[jira] [Updated] (SLING-10901) Allow terminating a GraphQL query after a configured timeout

     [ https://issues.apache.org/jira/browse/SLING-10901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andreas Schaefer updated SLING-10901:
-------------------------------------
    Fix Version/s: GraphQL Core 0.0.18
                       (was: GraphQL Core 0.0.16)

> Allow terminating a GraphQL query after a configured timeout
> ------------------------------------------------------------
>
>                 Key: SLING-10901
>                 URL: https://issues.apache.org/jira/browse/SLING-10901
>             Project: Sling
>          Issue Type: Improvement
>          Components: GraphQL
>            Reporter: Radu Cotescu
>            Assignee: Radu Cotescu
>            Priority: Major
>             Fix For: GraphQL Core 0.0.18
>
>
> Since expensive GraphQL queries could lead to a DoS attack, it would be worth allowing a system administrator to configure the maximum execution time of a query. When a long running query is interrupted, the returned error should be transparent for the GraphQL engine, so that the client knows exactly why the query failed.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)