From c1e07c86d94933469cda93b1fab8f9559f73a87d Mon Sep 17 00:00:00 2001 From: Outvi V <19144373+outloudvi@users.noreply.github.com> Date: Tue, 14 Jul 2020 23:58:25 +0800 Subject: [PATCH 1/2] Update link of serialization format in spec --- site/learn/BestPractice-Introduction.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/site/learn/BestPractice-Introduction.md b/site/learn/BestPractice-Introduction.md index b86e7e93d9..4053eed064 100644 --- a/site/learn/BestPractice-Introduction.md +++ b/site/learn/BestPractice-Introduction.md @@ -23,7 +23,7 @@ Read more about this in [Serving over HTTP](/learn/serving-over-http/). ### JSON (with GZIP) -GraphQL services typically respond using JSON, however the GraphQL spec [does not require it](http://facebook.github.io/graphql/#sec-Serialization-Format). JSON may seem like an odd choice for an API layer promising better network performance, however because it is mostly text, it compresses exceptionally well with GZIP. +GraphQL services typically respond using JSON, however the GraphQL spec [does not require it](http://spec.graphql.org/June2018/#sec-Serialization-Format). JSON may seem like an odd choice for an API layer promising better network performance, however because it is mostly text, it compresses exceptionally well with GZIP. It's encouraged that any production GraphQL services enable GZIP and encourage their clients to send the header: From b7682aa5896857756b38d28f3732e757e1f02c1b Mon Sep 17 00:00:00 2001 From: Ivan Goncharov Date: Wed, 2 Sep 2020 14:07:21 +0300 Subject: [PATCH 2/2] Update site/learn/BestPractice-Introduction.md --- site/learn/BestPractice-Introduction.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/site/learn/BestPractice-Introduction.md b/site/learn/BestPractice-Introduction.md index 4053eed064..6f06681a42 100644 --- a/site/learn/BestPractice-Introduction.md +++ b/site/learn/BestPractice-Introduction.md @@ -23,7 +23,7 @@ Read more about this in [Serving over HTTP](/learn/serving-over-http/). ### JSON (with GZIP) -GraphQL services typically respond using JSON, however the GraphQL spec [does not require it](http://spec.graphql.org/June2018/#sec-Serialization-Format). JSON may seem like an odd choice for an API layer promising better network performance, however because it is mostly text, it compresses exceptionally well with GZIP. +GraphQL services typically respond using JSON, however the GraphQL spec [does not require it](http://spec.graphql.org/draft/#sec-Serialization-Format). JSON may seem like an odd choice for an API layer promising better network performance, however because it is mostly text, it compresses exceptionally well with GZIP. It's encouraged that any production GraphQL services enable GZIP and encourage their clients to send the header: