* This report was auto-generated by graphql-http

• 60 audits in total
• ✅ 46 pass
• 💡 6 notices (suggestions)
• ❗️ 7 warnings (optional)
• ❌ 1 errors (required)

1. 4655 MUST accept application/json and match the content-type
2. 47DE SHOULD accept */* and use application/json for the content-type
3. 80D8 SHOULD assume application/json content-type when accept is missing
4. 82A3 MUST use utf-8 encoding when responding
5. BF61 MUST accept utf-8 encoded request
6. 78D5 MUST assume utf-8 in request if encoding is unspecified
7. 2C94 MUST accept POST requests
8. 5A70 MAY accept application/x-www-form-urlencoded formatted GET requests
9. 9C48 MAY NOT allow executing mutations on GET requests
10. 9ABE MAY respond with 4xx status code if content-type is not supplied on POST requests
11. 03D4 MUST accept application/json POST requests
12. A5BF MAY use 400 status code when request body is missing on POST
13. 423L MAY use 400 status code on missing {query} parameter
14. LKJ0 MAY use 400 status code on object {query} parameter
15. LKJ3 MAY use 400 status code on array {query} parameter
16. 34A2 SHOULD allow string {query} parameter when accepting application/graphql-response+json
17. 13EE MUST allow string {query} parameter when accepting application/json
18. 6C00 MAY use 400 status code on object {operationName} parameter
19. 6C03 MAY use 400 status code on array {operationName} parameter
20. 8161 SHOULD allow string {operationName} parameter when accepting application/graphql-response+json
21. B8B3 MUST allow string {operationName} parameter when accepting application/json
22. 94B0 SHOULD allow null {variables} parameter when accepting application/graphql-response+json
23. 0220 MUST allow null {variables} parameter when accepting application/json
24. 94B1 SHOULD allow null {operationName} parameter when accepting application/graphql-response+json
25. 0221 MUST allow null {operationName} parameter when accepting application/json
26. 4760 MAY use 400 status code on string {variables} parameter
27. 4763 MAY use 400 status code on array {variables} parameter
28. 2EA1 SHOULD allow map {variables} parameter when accepting application/graphql-response+json
29. 28B9 MUST allow map {variables} parameter when accepting application/json
30. D6D5 MAY allow URL-encoded JSON string {variables} parameter in GETs when accepting application/graphql-response+json
31. 6A70 MAY allow URL-encoded JSON string {variables} parameter in GETs when accepting application/json
32. 58B0 MAY use 400 status code on string {extensions} parameter
33. 58B1 MAY use 400 status code on number {extensions} parameter
34. 58B2 MAY use 400 status code on boolean {extensions} parameter
35. 58B3 MAY use 400 status code on array {extensions} parameter
36. 428F SHOULD allow map {extensions} parameter when accepting application/graphql-response+json
37. 1B7A MUST allow map {extensions} parameter when accepting application/json
38. B6DC MAY use 4xx or 5xx status codes on JSON parsing failure
39. BCF8 MAY use 400 status code on JSON parsing failure
40. 8764 MAY use 4xx or 5xx status codes if parameters are invalid
41. 3E3A MAY use 400 status code if parameters are invalid
42. 7B9B SHOULD use a status code of 200 on variable coercion failure when accepting application/json
43. 865D SHOULD use 4xx or 5xx status codes on document parsing failure when accepting application/graphql-response+json
44. 556A SHOULD use 400 status code on document parsing failure when accepting application/graphql-response+json
45. 51FE SHOULD use 4xx or 5xx status codes on document validation failure when accepting application/graphql-response+json
46. 74FF SHOULD use 400 status code on document validation failure when accepting application/graphql-response+json

1. LKJ1 MAY use 400 status code on number {query} parameter
   Response status code is not 400

   {
     "statusText": "OK",
     "status": 200,
     "headers": {
       "keep-alive": "timeout=72",
       "date": "",
       "content-type": "application/json; charset=utf-8",
       "content-length": "61",
       "connection": "keep-alive"
     },
     "body": {
       "errors": [
         {
           "message": "Must provide document."
         }
       ],
       "data": null
     }
   }
   

2. LKJ2 MAY use 400 status code on boolean {query} parameter
   Response status code is not 400

   {
     "statusText": "OK",
     "status": 200,
     "headers": {
       "keep-alive": "timeout=72",
       "date": "",
       "content-type": "application/json; charset=utf-8",
       "content-length": "61",
       "connection": "keep-alive"
     },
     "body": {
       "errors": [
         {
           "message": "Must provide document."
         }
       ],
       "data": null
     }
   }
   

3. 6C01 MAY use 400 status code on number {operationName} parameter
   Response status code is not 400

   {
     "statusText": "OK",
     "status": 200,
     "headers": {
       "keep-alive": "timeout=72",
       "date": "",
       "content-type": "application/json; charset=utf-8",
       "content-length": "69",
       "connection": "keep-alive"
     },
     "body": {
       "errors": [
         {
           "message": "Unknown operation named \"0\"."
         }
       ],
       "data": null
     }
   }
   

4. 6C02 MAY use 400 status code on boolean {operationName} parameter
   Response status code is not 400

   {
     "statusText": "OK",
     "status": 200,
     "headers": {
       "keep-alive": "timeout=72",
       "date": "",
       "content-type": "application/json; charset=utf-8",
       "content-length": "73",
       "connection": "keep-alive"
     },
     "body": {
       "errors": [
         {
           "message": "Unknown operation named \"false\"."
         }
       ],
       "data": null
     }
   }
   

5. 4761 MAY use 400 status code on number {variables} parameter
   Response status code is not 400

   {
     "statusText": "OK",
     "status": 200,
     "headers": {
       "keep-alive": "timeout=72",
       "date": "",
       "content-type": "application/json; charset=utf-8",
       "content-length": "31",
       "connection": "keep-alive"
     },
     "body": {
       "data": {
         "__typename": "Query"
       }
     }
   }
   

6. 4762 MAY use 400 status code on boolean {variables} parameter
   Response status code is not 400

   {
     "statusText": "OK",
     "status": 200,
     "headers": {
       "keep-alive": "timeout=72",
       "date": "",
       "content-type": "application/json; charset=utf-8",
       "content-length": "31",
       "connection": "keep-alive"
     },
     "body": {
       "data": {
         "__typename": "Query"
       }
     }
   }
   

1. 22EB SHOULD accept application/graphql-response+json and match the content-type
   Response header content-type does not contain application/graphql-response+json

   {
     "statusText": "OK",
     "status": 200,
     "headers": {
       "keep-alive": "timeout=72",
       "date": "",
       "content-type": "application/json; charset=utf-8",
       "content-length": "31",
       "connection": "keep-alive"
     },
     "body": {
       "data": {
         "__typename": "Query"
       }
     }
   }
   

2. 94B2 SHOULD allow null {extensions} parameter when accepting application/graphql-response+json
   Response status code is not 200

   {
     "statusText": "Bad Request",
     "status": 400,
     "headers": {
       "keep-alive": "timeout=72",
       "date": "",
       "content-type": "application/json; charset=utf-8",
       "content-length": "69",
       "connection": "keep-alive"
     },
     "body": {
       "errors": [
         {
           "message": "body/extensions must be object"
         }
       ],
       "data": null
     }
   }
   

3. 572B SHOULD use 200 status code on document parsing failure when accepting application/json
   Response status code is not 200

   {
     "statusText": "Bad Request",
     "status": 400,
     "headers": {
       "keep-alive": "timeout=72",
       "date": "",
       "content-type": "application/json; charset=utf-8",
       "content-length": "116",
       "connection": "keep-alive"
     },
     "body": {
       "errors": [
         {
           "message": "Syntax Error: Expected Name, found .",
           "locations": [
             {
               "line": 1,
               "column": 2
             }
           ]
         }
       ],
       "data": null
     }
   }
   

4. FDE2 SHOULD use 200 status code on document validation failure when accepting application/json
   Response status code is not 200

   {
     "statusText": "Bad Request",
     "status": 400,
     "headers": {
       "keep-alive": "timeout=72",
       "date": "",
       "content-type": "application/json; charset=utf-8",
       "content-length": "135",
       "connection": "keep-alive"
     },
     "body": {
       "errors": [
         {
           "message": "Syntax Error: Invalid number, expected digit but got: \"f\".",
           "locations": [
             {
               "line": 1,
               "column": 4
             }
           ]
         }
       ],
       "data": null
     }
   }
   

5. D586 SHOULD not contain the data entry on document parsing failure when accepting application/graphql-response+json
   Response body execution result data is not "undefined"

   {
     "statusText": "Bad Request",
     "status": 400,
     "headers": {
       "keep-alive": "timeout=72",
       "date": "",
       "content-type": "application/json; charset=utf-8",
       "content-length": "116",
       "connection": "keep-alive"
     },
     "body": {
       "errors": [
         {
           "message": "Syntax Error: Expected Name, found .",
           "locations": [
             {
               "line": 1,
               "column": 2
             }
           ]
         }
       ],
       "data": null
     }
   }
   

6. 5E5B SHOULD not contain the data entry on document validation failure when accepting application/graphql-response+json
   Response body execution result data is not "undefined"

   {
     "statusText": "Bad Request",
     "status": 400,
     "headers": {
       "keep-alive": "timeout=72",
       "date": "",
       "content-type": "application/json; charset=utf-8",
       "content-length": "135",
       "connection": "keep-alive"
     },
     "body": {
       "errors": [
         {
           "message": "Syntax Error: Invalid number, expected digit but got: \"f\".",
           "locations": [
             {
               "line": 1,
               "column": 4
             }
           ]
         }
       ],
       "data": null
     }
   }
   

7. 86EE SHOULD use a status code of 400 on variable coercion failure when accepting application/graphql-response+json
   Response status code is not 400

   {
     "statusText": "OK",
     "status": 200,
     "headers": {
       "keep-alive": "timeout=72",
       "date": "",
       "content-type": "application/json; charset=utf-8",
       "content-length": "210",
       "connection": "keep-alive"
     },
     "body": {
       "errors": [
         {
           "message": "Unknown type \"ID\".",
           "locations": [
             {
               "line": 1,
               "column": 26
             }
           ]
         },
         {
           "message": "Variable \"$id\" is never used in operation \"CoerceFailure\".",
           "locations": [
             {
               "line": 1,
               "column": 21
             }
           ]
         }
       ],
       "data": null
     }
   }
   

1. 0222 MUST allow null {extensions} parameter when accepting application/json
   Response status code is not 200

   {
     "statusText": "Bad Request",
     "status": 400,
     "headers": {
       "keep-alive": "timeout=72",
       "date": "",
       "content-type": "application/json; charset=utf-8",
       "content-length": "69",
       "connection": "keep-alive"
     },
     "body": {
       "errors": [
         {
           "message": "body/extensions must be object"
         }
       ],
       "data": null
     }
   }