-
Notifications
You must be signed in to change notification settings - Fork 320
HttpGraphQlClient content-type #389
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
Comments
The Lines 59 to 71 in 8549060
As of #359, you can explicitly set a content type with the client, so this might be a duplicate of this issue. Is there something else we're missing? Can you try our latest SNAPSHOTs? |
Thanks, I can confirm that the issue is fixed on SNAPSHOT. |
Thanks for trying the SNAPSHOTs! |
The content-type header in HttpGraphQlTransport is hard-code to application/graphql+json. No all graphql servers supports application/graphql+json. Can we make the content-type configurable?
The text was updated successfully, but these errors were encountered: