Skip to content

Commit ee805e2

Browse files
Update src/pages/learn/file-uploads.mdx
Co-authored-by: Benjie <[email protected]>
1 parent 915873e commit ee805e2

File tree

1 file changed

+5
-3
lines changed

1 file changed

+5
-3
lines changed

src/pages/learn/file-uploads.mdx

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -14,9 +14,11 @@ File uploads, by contrast, typically handle binary data such as images and PDFs
1414
One option is to encode within our encoding (e.g. use a base64-encoded string within our JSON), but this is inefficient and is not suitable for larger binary files as it does not support streamed processing easily.
1515
Instead, `multipart/form-data` is a common choice for transferring binary data; but it is not without its own set of complexities.
1616

17-
Supporting uploads over GraphQL usually involves adopting community conventions, like the
18-
[GraphQL multipart request specification](https://github.com/jaydenseric/graphql-multipart-request-spec). While useful in some
19-
environments, these solutions often introduce complexity, fragility, and security risks.
17+
Supporting uploads over GraphQL usually involves adopting community conventions, the most prevalent of which is the
18+
[GraphQL multipart request specification](https://github.com/jaydenseric/graphql-multipart-request-spec).
19+
This specification has been successfully implemented in many languages and frameworks, but users
20+
implementing it must pay very close attention to ensure that they do not introduce
21+
security or reliability concerns.
2022

2123
## Risks to be aware of
2224

0 commit comments

Comments
 (0)