Skip to content
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

GraphQL playground and StrawberryShake HttpVersion #2445

Closed
compgumby opened this issue Oct 16, 2020 · 0 comments · Fixed by #6641
Closed

GraphQL playground and StrawberryShake HttpVersion #2445

compgumby opened this issue Oct 16, 2020 · 0 comments · Fixed by #6641

Comments

@compgumby
Copy link

compgumby commented Oct 16, 2020

I have a complex situation. HotChocolate serving up GraphQL on a stateless service fabric service API. Since it's an API behind the service fabric load balancer, there's port forwarding. It's all HTTPS. The endpoint is backed by a CA certificate. Locally, I just expose a regular HTTP port and all is well. In the cloud, it's HTTPS and backed by a cert behind the load balancer.

With Postman, I can get it to work. Playground and Voyager do not, although using Fiddler, I can see the schema getting returned from the endpoint - but for whatever reason, Playground can't parse it - Chrome says ERR_INCOMPLETE_CHUNKED_ENCODING.

From StrawberryShake, I can't do anything UNLESS I hack the InvokeAsync method of SendHttpRequestMiddleware and set the HttpVersion to HttpVersion.Version10. At this point, things are fine. However, everything runs locally just fine without having to jump through that hoop. Whether it's because the real deployment is behind a forwarded port, or because it's secured by a cert, or because it's just not local... I have no idea. Fiddler shows data coming back, but that Chunk error is an issue.

We'd like to use HotChocolate and the rest of the suite (sweet?), but these pain points are becoming critical.

Update
It may be Fiddler was causing the chunking error. But without Fiddler, I get this:
ERR_HTTP2_PROTOCOL_ERROR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants