From 3501d43f9767770a280b66aa6377a13053f86658 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Mads=20M=C3=B8rch=20Schou?= Date: Thu, 17 Oct 2024 10:07:49 +0200 Subject: [PATCH] Update umbraco-heartcore/api-documentation/graphql/persisted-queries.md Co-authored-by: jonat123 <54025331+jonat123@users.noreply.github.com> --- .../api-documentation/graphql/persisted-queries.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/umbraco-heartcore/api-documentation/graphql/persisted-queries.md b/umbraco-heartcore/api-documentation/graphql/persisted-queries.md index 178b94f74d..722f9bced4 100644 --- a/umbraco-heartcore/api-documentation/graphql/persisted-queries.md +++ b/umbraco-heartcore/api-documentation/graphql/persisted-queries.md @@ -14,7 +14,7 @@ Persisted queries allow you to store GraphQL queries on the server. This enables * Enhanced Security - Persisted queries provide improved security by ensuring that only predefined, server-stored GraphQL queries can be executed, preventing clients from running arbitrary or malicious queries. + * Persisted queries provide improved security by ensuring that only predefined, server-stored GraphQL queries can be executed, preventing clients from running arbitrary or malicious queries. To fully benefit from this, the content delivery API must be set to private, and GraphQL must be configured only to allow persisted queries. Without these settings in place, the security advantages of using persisted queries are not realized.