* This report was auto-generated by graphql-http
- 60 audits in total
- ✅ 57 pass
- 💡 3 notices (suggestions)
22EBSHOULD accept application/graphql-response+json and match the content-type4655MUST accept application/json and match the content-type47DESHOULD accept */* and use application/json for the content-type80D8SHOULD assume application/json content-type when accept is missing82A3MUST use utf-8 encoding when respondingBF61MUST accept utf-8 encoded request78D5MUST assume utf-8 in request if encoding is unspecified2C94MUST accept POST requests5A70MAY accept application/x-www-form-urlencoded formatted GET requests9C48MAY NOT allow executing mutations on GET requests9ABEMAY respond with 4xx status code if content-type is not supplied on POST requests03D4MUST accept application/json POST requests423LMAY use 400 status code on missing {query} parameterLKJ0MAY use 400 status code on object {query} parameterLKJ1MAY use 400 status code on number {query} parameterLKJ2MAY use 400 status code on boolean {query} parameterLKJ3MAY use 400 status code on array {query} parameter34A2SHOULD allow string {query} parameter when accepting application/graphql-response+json13EEMUST allow string {query} parameter when accepting application/json6C00MAY use 400 status code on object {operationName} parameter6C01MAY use 400 status code on number {operationName} parameter6C02MAY use 400 status code on boolean {operationName} parameter6C03MAY use 400 status code on array {operationName} parameter8161SHOULD allow string {operationName} parameter when accepting application/graphql-response+jsonB8B3MUST allow string {operationName} parameter when accepting application/json94B0SHOULD allow null {variables} parameter when accepting application/graphql-response+json0220MUST allow null {variables} parameter when accepting application/json94B1SHOULD allow null {operationName} parameter when accepting application/graphql-response+json0221MUST allow null {operationName} parameter when accepting application/json94B2SHOULD allow null {extensions} parameter when accepting application/graphql-response+json0222MUST allow null {extensions} parameter when accepting application/json4760MAY use 400 status code on string {variables} parameter4761MAY use 400 status code on number {variables} parameter4762MAY use 400 status code on boolean {variables} parameter4763MAY use 400 status code on array {variables} parameter2EA1SHOULD allow map {variables} parameter when accepting application/graphql-response+json28B9MUST allow map {variables} parameter when accepting application/jsonD6D5MAY allow URL-encoded JSON string {variables} parameter in GETs when accepting application/graphql-response+json6A70MAY allow URL-encoded JSON string {variables} parameter in GETs when accepting application/json58B0MAY use 400 status code on string {extensions} parameter58B1MAY use 400 status code on number {extensions} parameter58B2MAY use 400 status code on boolean {extensions} parameter58B3MAY use 400 status code on array {extensions} parameter428FSHOULD allow map {extensions} parameter when accepting application/graphql-response+json1B7AMUST allow map {extensions} parameter when accepting application/json8764MAY use 4xx or 5xx status codes if parameters are invalid3E3AMAY use 400 status code if parameters are invalid572BSHOULD use 200 status code on document parsing failure when accepting application/jsonFDE2SHOULD use 200 status code on document validation failure when accepting application/json7B9BSHOULD use a status code of 200 on variable coercion failure when accepting application/json865DSHOULD use 4xx or 5xx status codes on document parsing failure when accepting application/graphql-response+json556ASHOULD use 400 status code on document parsing failure when accepting application/graphql-response+jsonD586SHOULD not contain the data entry on document parsing failure when accepting application/graphql-response+json51FESHOULD use 4xx or 5xx status codes on document validation failure when accepting application/graphql-response+json74FFSHOULD use 400 status code on document validation failure when accepting application/graphql-response+json5E5BSHOULD not contain the data entry on document validation failure when accepting application/graphql-response+json86EESHOULD use a status code of 400 on variable coercion failure when accepting application/graphql-response+json
A5BFMAY use 400 status code when request body is missing on POSTResponse status code is not 400
{ "statusText": "OK", "status": 200, "headers": { "keep-alive": "timeout=5", "date": "", "content-type": "application/json; charset=utf-8", "content-length": "55", "connection": "keep-alive" }, "body": { "errors": [ { "message": "POST body sent invalid JSON." } ] } }B6DCMAY use 4xx or 5xx status codes on JSON parsing failureResponse status is not between 400 and 499
{ "statusText": "OK", "status": 200, "headers": { "keep-alive": "timeout=5", "date": "", "content-type": "application/json; charset=utf-8", "content-length": "55", "connection": "keep-alive" }, "body": { "errors": [ { "message": "POST body sent invalid JSON." } ] } }BCF8MAY use 400 status code on JSON parsing failureResponse status code is not 400
{ "statusText": "OK", "status": 200, "headers": { "keep-alive": "timeout=5", "date": "", "content-type": "application/json; charset=utf-8", "content-length": "55", "connection": "keep-alive" }, "body": { "errors": [ { "message": "POST body sent invalid JSON." } ] } }