MapGraphQL vs MapGraphQLHttp and MapGraphQLWebSocket

[RehanSaeed]

Is it possible to have MapGraphQLHttp and MapGraphQLWebSocket co-exist at /graphql just like MapGraphQL used to do? A lot of GraphQL tools prefer this. When I try it I get an exception:

Microsoft.AspNetCore.Routing.Matching.AmbiguousMatchException: The request matched multiple endpoints. Matches:

Hot Chocolate GraphQL HTTP Pipeline
Hot Chocolate GraphQL WebSocket Pipeline

In theory mapping them both to the same URL should be ok because the use different schemes.

• https://localhost/graphql
• ws://localhost/graphql

[OlegLviv]

any updates?

[tobias-tengler]

Not as far as I know, but I've properly raised an issue about it, so we can track it better :) #4707

[michaelstaib]

Not planned since you have MapGraphQL for it. We created MapGraphQLHttp and MapGraphQLWebSocket to explicitly not have them on the same route.

If you want to have them on the same route use MapGraphQL and pass in options for things you want to exclude.

[OlegLviv]

builder.UseEndpoints(endpoints => { endpoints.MapGraphQL<GraphQlSchema>(); });


My front-end app can't establish a connection through ws because I have not registered the route so I need to separate them
but before I updated GraphQL NuGet packages it works... how?

[michaelstaib]

If you just use MapGraphQL everything will be configured on a single endpoint.

[michaelstaib]

Not planned since you have MapGraphQL for it. We created MapGraphQLHttp and MapGraphQLWebSocket to explicitly not have them on the same route.

If you want to have them on the same route use MapGraphQL and pass in options for things you want to exclude.