server icon indicating copy to clipboard operation
server copied to clipboard

ASP.NET Core GraphQL Server

Results 44 server issues
Sort by recently updated
recently updated
newest added

Bumps [Serilog.AspNetCore](https://github.com/serilog/serilog-aspnetcore), [Microsoft.Extensions.DependencyInjection](https://github.com/dotnet/runtime) and [Serilog.Sinks.Console](https://github.com/serilog/serilog-sinks-console). These dependencies needed to be updated together. Updates `Serilog.AspNetCore` from 7.0.0 to 8.0.1 Release notes Sourced from Serilog.AspNetCore's releases. v8.0.1 #357 - bug fix: generate...

dependencies
.NET

We are using the Server.All package to allow our users to be able to pick their GraphQL UI from Altair, Playground and GraphiQL. We have an asp .net core application...

Requires GraphQL.NET 8.x Other changes required since extension methods were moved from `IProvideMetadata` to `IMetadataReader` in v8. Tests not finished yet

There was [`IOperationMessageListener`](https://github.com/graphql-dotnet/server/blob/v6/src/Transports.Subscriptions.Abstractions/IOperationMessageListener.cs) in v6 and some our code uses it. Now I need to migrate that code to the-latest-and-greatest v7. My main goal is to achieve the "old behavior"...

See: https://www.apollographql.com/docs/apollo-server/security/cors/#preventing-cross-site-request-forgery-csrf

See notes for `GraphQLHttpMiddlewareOptions.ReadFormOnPost` (which may be inaccurate). See https://www.apollographql.com/blog/backend/file-uploads/file-upload-best-practices Based on CORS spec, I actually think CORS would be triggered if cookies were sent, but I'm not sure. Assuming...

See: - #993 This 'resolves' the issue noticed by @triumphtang and @yuchen-w in #993 at the cost of returning Forbidden instead of Unauthorized for typical implementations when policy/role requirements are...

test

Hi guys, It is very strange when my HTTP response codes are not corresponding to the error I want to return to the front end. How can I change that?...

question

Not sure if it's a bug or a misunderstanding of the spec. I'm migrating from 5.1.1 to 7.2.0 and found that in some cases, the HttpStatus Code changed from 200...

enhancement
question
spec compliance

Fix for issue https://github.com/graphql-dotnet/server/issues/1129