GraphQL Error on HTTP 200 and correct json schema wrapped in error

[dillonkearns]

GraphQL Error on HTTP 200 and correct json schema wrapped in error

[dillonkearns]

Hey @rofrol thanks for reporting the issue and for the all the details.

Graphqelm appears to be handling that response as I would expect. The response is telling it that there is an error, and the fact that the actual response is nested in there means that Juniper is capable of generating the response, but as far as the client (Graphqelm) is concerned, it has no way to know to find the response there. So as best I can tell, this appears to be an issue with Juniper. Or perhaps there is some header or something that needs to be passed to make Juniper happy? It is surprising because it understands the request based on the fact that it actually gives the response. And it doesn't give any details of the error.

I'm not really sure what to do with this on my end as it appears to be handling it properly on the Graphqelm side. Could you try to figure out why it's sending the response back nested under error? Perhaps you could file an issue on the Juniper or actix-web repo? I'd be happy to help if there's an issue on the Graphqelm-side but as far as I can understand there doesn't appear to be. Thanks!

[rofrol]

That's strange, because downloading schema with fetch-graphql-schema or the code I've created https://github.com/rofrol/fetch-graphql-schema-custom, works.

[rofrol]

Headers received from juniper when running query inside chrome dev tools console:

HTTP/1.1 200 OK
content-length: 157
content-encoding: br
date: Sun, 01 Apr 2018 13:11:29 GMT

When used cross-fetch, encoding set to gzip.

[rofrol]

I think this is the issue:

  if (contentType && contentType.startsWith('application/json')) {
    return response.json()
  } else {
    return response.text()
  }

https://github.com/graphcool/graphql-request/blob/9e689c94e5d90b3a238a1386b92a27bc96d8c20d/src/index.ts#L120

because it may be content-encoding: gzip

[rofrol]

Closing in favor of jasonkuhrt/graphql-request#70

[dillonkearns]

Interesting, thanks for investigating @rofrol! Keep me posted, I'm curious to see how this gets resolved.