Skip to content

Commit 490f08c

Browse files
authored
Removed incorrect HTTP header syntax from a note (#2061)
The Accept HTTP header does not support "charset" directives, only media types and the "q" directive, so ";charset=utf-8" was removed.
1 parent a3d6819 commit 490f08c

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

src/pages/learn/serving-over-http.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ GraphQL clients and servers should support JSON for serialization and may suppor
3131
If no encoding information is included with this header, then it will be assumed to be `utf-8`. However, the server may respond with an error if a client doesn't provide the `Accept` header with a request.
3232

3333
<Callout type="info">
34-
The `application/graphql-response+json` is described in the draft GraphQL over HTTP specification. To ensure compatibility, if a client sends a request to a legacy GraphQL server before 1st January 2025, the `Accept` header should also include the `application/json` media type as follows: `application/graphql-response+json;charset=utf-8, application/json;charset=utf-8`
34+
The `application/graphql-response+json` is described in the draft GraphQL over HTTP specification. To ensure compatibility, if a client sends a request to a legacy GraphQL server before 1st January 2025, the `Accept` header should also include the `application/json` media type as follows: `application/graphql-response+json, application/json`
3535
</Callout>
3636

3737
### Methods

0 commit comments

Comments
 (0)