You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's still coming over as application/graphql+json.
We need to do this, as the the Apollo graphql gateway we're using does not accept the graphql header.
Error: POST body missing, invalid Content-Type, or JSON object has no keys. (it's not the other two).
The text was updated successfully, but these errors were encountered:
rstoyanchev
changed the title
Client - Update documentation on how to override Content Type Header
HttpGraphQlClientTransport should allow explicitly set Content-Type
Apr 28, 2022
rstoyanchev
changed the title
HttpGraphQlClientTransport should allow explicitly set Content-Type
HttpGraphQlClientTransport should respect an existing, explicitly set Content-Type
May 16, 2022
Uh oh!
There was an error while loading. Please reload this page.
With
1.0.0-RC1
, the Client now sends theContent-Type
header asapplication/graphql+json
We're trying to override the headers here, but it has no affect:
It's still coming over as
application/graphql+json
.We need to do this, as the the Apollo graphql gateway we're using does not accept the
graphql
header.Error:
POST body missing, invalid Content-Type, or JSON object has no keys.
(it's not the other two).The text was updated successfully, but these errors were encountered: