Alexander Rose

@JonathanDuvalV does this issue still persist with the latest release? There have been some changes regarding threading with subscriptions...

use the latest, currently 3.1.9

A better workaround would be to override [GraphQLHttpRequest.ToHttpRequestMessage](https://github.com/graphql-dotnet/graphql-client/blob/812a7400f307fc10d94d80f0ce095006f8d85fd2/src/GraphQL.Client/GraphQLHttpRequest.cs#L37), that's where the charset is specified.

Btw, the [GraphQL Spec](https://spec.graphql.org/June2018/#sec-String) defines strings as *UTF‐8 character sequences*...

Well... you added an `Authorization` header... But I suppose you'd need to add a `x-developer-secret` header instead?

```csharp var request = new GraphQLRequest{ Query = "your query string", OperationName = "your operation name", Variables = new { variable1 = "value for variable1", variable2 = 1337 } }...

This is a common issue with navigation properties (1 - n) in entity framework! If you use this on a entity with said relationship in a unit test, the test...

I second this feature request, my actual use case would be to link a task to a related GitLab issue ...

I think graphql-dotnet/server#480 is not enough to solve this one... [GraphQLHttpMiddleware](https://github.com/graphql-dotnet/server/blob/master/src/Transports.AspNetCore/GraphQLHttpMiddleware.cs) will still respond with a 200 status code... You can only change the message text which is reported inside...

Any updates on this? I have a build script which vitally depends on your binaries...