Tobias Tengler

Adding the ability to specify a default type was what I was proposing above 😅 I think at the moment you sadly have to specify the type explicitly...

## ~~No Accept Header + `@defer` leads to exception~~ Fixed by: 13.0.0-preview.50 Not specifying an `Accept` header when sending a request containing `@defer` in Chrome leads to HTTP 500 and...

## Validation errors produce wrong status code with Accept `multipart/mixed` Sending an invalid GraphQL query in combination with the `multipart/mixed` Accept header yields a status code of 200, which should...

## ~~400 status code for GraphQL errors when Accept header is omitted~~ Fixed by: 13.0.0-preview.50 In [this section](https://github.com/graphql/graphql-over-http/blob/main/spec/GraphQLOverHTTP.md#legacy-watershed-1) the spec states: > Before 1st January 2025 (2025-01-01T00:00:00Z), if the client...

## ~~Deferred fields leak between requests if previous request throws exception~~ Fixed by: 13.0.0-preview.50 The following query ```graphql { field1 ... @defer { field2 } } ``` can produce the...

## ~~Deferred responses might not be correctly processed by the browser~~ Fixed by: 13.0.0-preview.58 **This could be an issue with the browser, meros or Hot Chocolate: I can't say with...

## ~~Full deferred query result is returned for other request~~ I could no longer reproduce this, so I think it should be addressed... **Can't reproduce this reliably yet, but it...

## ~~Unsupported Accept header starting with `application` or `multipart` = 500~~ No Accept header value or a value of `this is not an accept header value` is correctly treated as...

I have just created https://github.com/graphql/graphql-over-http/issues/228 because I think it would make sense to have a shared collection of test cases that server maintainers can reference.

@michaelstaib is it supposed to HTTP 400, if I send two supported Accept header values? ``` Accept: "application/graphql-response+json, mulitpart/mixed" ``` I want to signal to the server that I support...