-
-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Curl example #6
Comments
In the meantime, you might find the |
@lunchboxer Here is an example, I copied from Postman. ^_^
Ps: Replace files |
- Examples match those of https://github.com/jaydenseric/apollo-upload-examples. - Added example cURL requests, fixing #6. - Added example request payloads.
Done! The examples now match those of apollo-upload-examples, and they each display a cURL request. |
im getting:
when executing curl any idea? @jaydenseric |
@gustavomc No solid ideas, but are you sure |
I am getting below error with above curl command
{"errors":[{"message":"GraphQL Request must include at least one of those two parameters: "query" or "queryId"","category":"request"}]} |
@gohelkiran30 that might be because the server is not configured to handle multipart requests. Have you setup the |
I havn't used any middleware, I am firing a request from console using a curl command hence no middleware required. |
The GraphQL server that you are sending the request to (http://localhost:3001/graphql) needs to support GraphQL multipart requests, typically via middleware. Comments in existing issues in this repo is not the right place to asking such usage questions. |
ok, I will create a new issue |
@gustavomc |
@gohelkiran30 @giautm I noticed you both are using
and actually in the curl example given, you can remove the variable part for
but
|
@sunapi386 follow the example in the spec: https://github.com/jaydenseric/graphql-multipart-request-spec#curl-request-1 |
@jaydenseric my bad, I mistyped Very subtle error. |
The readme could be improved by adding an example of usage with CURL. I myself am having difficulty figuring out exactly how it would look.
The text was updated successfully, but these errors were encountered: