|
| 1 | +_* This report was auto-generated by graphql-http_ |
| 2 | + |
| 3 | +# GraphQL over HTTP audit report |
| 4 | + |
| 5 | +- **79** audits in total |
| 6 | +- ✅ **32** pass |
| 7 | +- ⚠️ **44** warnings (optional) |
| 8 | +- ❌ **3** errors (required) |
| 9 | + |
| 10 | +## Passing |
| 11 | +1. MUST accept application/json and match the content-type |
| 12 | +2. SHOULD accept \*/\* and use application/json for the content-type |
| 13 | +3. SHOULD assume application/json content-type when accept is missing |
| 14 | +4. MUST accept POST requests |
| 15 | +5. MAY accept application/x-www-form-urlencoded formatted GET requests |
| 16 | +6. MAY NOT allow executing mutations on GET requests |
| 17 | +7. SHOULD respond with 4xx status code if content-type is not supplied on POST requests |
| 18 | +8. MUST accept application/json POST requests |
| 19 | +9. MUST require a request body on POST |
| 20 | +10. SHOULD use 200 status code with errors field on missing {query} parameter when accepting application/json |
| 21 | +11. SHOULD use 200 status code with errors field on object {query} parameter when accepting application/json |
| 22 | +12. SHOULD use 200 status code with errors field on number {query} parameter when accepting application/json |
| 23 | +13. SHOULD use 200 status code with errors field on boolean {query} parameter when accepting application/json |
| 24 | +14. SHOULD use 200 status code with errors field on array {query} parameter when accepting application/json |
| 25 | +15. MUST allow string {query} parameter when accepting application/json |
| 26 | +16. SHOULD use 200 status code with errors field on object {operationName} parameter when accepting application/json |
| 27 | +17. SHOULD use 200 status code with errors field on number {operationName} parameter when accepting application/json |
| 28 | +18. SHOULD use 200 status code with errors field on boolean {operationName} parameter when accepting application/json |
| 29 | +19. SHOULD use 200 status code with errors field on array {operationName} parameter when accepting application/json |
| 30 | +20. MUST allow string {operationName} parameter when accepting application/json |
| 31 | +21. MUST allow null {variables} parameter when accepting application/json |
| 32 | +22. MUST allow null {operationName} parameter when accepting application/json |
| 33 | +23. MUST allow null {extensions} parameter when accepting application/json |
| 34 | +24. MUST allow map {variables} parameter when accepting application/json |
| 35 | +25. MUST allow map {extensions} parameter when accepting application/json |
| 36 | +26. SHOULD use 200 status code if parameters are invalid when accepting application/json |
| 37 | +27. SHOULD use 200 status code on document parsing failure when accepting application/json |
| 38 | +28. SHOULD use 200 status code on document validation failure when accepting application/json |
| 39 | +29. SHOULD use 4xx or 5xx status codes on JSON parsing failure when accepting application/graphql-response+json |
| 40 | +30. SHOULD use 4xx or 5xx status codes if parameters are invalid when accepting application/graphql-response+json |
| 41 | +31. SHOULD use 4xx or 5xx status codes on document parsing failure when accepting application/graphql-response+json |
| 42 | +32. SHOULD use 4xx or 5xx status codes on document validation failure when accepting application/graphql-response+json |
| 43 | + |
| 44 | +## Warnings |
| 45 | +The server _SHOULD_ support these, but is not required. |
| 46 | +1. SHOULD accept application/graphql-response+json and match the content-type<br /> |
| 47 | +``` |
| 48 | +Status code 406 is not 200 |
| 49 | +``` |
| 50 | +2. SHOULD use 400 status code on missing {query} parameter when accepting application/graphql-response+json<br /> |
| 51 | +``` |
| 52 | +Status code 406 is not 400 |
| 53 | +``` |
| 54 | +3. SHOULD use 400 status code on object {query} parameter when accepting application/graphql-response+json<br /> |
| 55 | +``` |
| 56 | +Status code 406 is not 400 |
| 57 | +``` |
| 58 | +4. SHOULD use 400 status code on number {query} parameter when accepting application/graphql-response+json<br /> |
| 59 | +``` |
| 60 | +Status code 406 is not 400 |
| 61 | +``` |
| 62 | +5. SHOULD use 400 status code on boolean {query} parameter when accepting application/graphql-response+json<br /> |
| 63 | +``` |
| 64 | +Status code 406 is not 400 |
| 65 | +``` |
| 66 | +6. SHOULD use 400 status code on array {query} parameter when accepting application/graphql-response+json<br /> |
| 67 | +``` |
| 68 | +Status code 406 is not 400 |
| 69 | +``` |
| 70 | +7. SHOULD allow string {query} parameter when accepting application/graphql-response+json<br /> |
| 71 | +``` |
| 72 | +Status code 406 is not 200 |
| 73 | +``` |
| 74 | +8. SHOULD use 400 status code on object {operationName} parameter when accepting application/graphql-response+json<br /> |
| 75 | +``` |
| 76 | +Status code 406 is not 400 |
| 77 | +``` |
| 78 | +9. SHOULD use 400 status code on number {operationName} parameter when accepting application/graphql-response+json<br /> |
| 79 | +``` |
| 80 | +Status code 406 is not 400 |
| 81 | +``` |
| 82 | +10. SHOULD use 400 status code on boolean {operationName} parameter when accepting application/graphql-response+json<br /> |
| 83 | +``` |
| 84 | +Status code 406 is not 400 |
| 85 | +``` |
| 86 | +11. SHOULD use 400 status code on array {operationName} parameter when accepting application/graphql-response+json<br /> |
| 87 | +``` |
| 88 | +Status code 406 is not 400 |
| 89 | +``` |
| 90 | +12. SHOULD allow string {operationName} parameter when accepting application/graphql-response+json<br /> |
| 91 | +``` |
| 92 | +Status code 406 is not 200 |
| 93 | +``` |
| 94 | +13. SHOULD allow null {variables} parameter when accepting application/graphql-response+json<br /> |
| 95 | +``` |
| 96 | +Status code 406 is not 200 |
| 97 | +``` |
| 98 | +14. SHOULD allow null {operationName} parameter when accepting application/graphql-response+json<br /> |
| 99 | +``` |
| 100 | +Status code 406 is not 200 |
| 101 | +``` |
| 102 | +15. SHOULD allow null {extensions} parameter when accepting application/graphql-response+json<br /> |
| 103 | +``` |
| 104 | +Status code 406 is not 200 |
| 105 | +``` |
| 106 | +16. SHOULD use 400 status code on string {variables} parameter when accepting application/graphql-response+json<br /> |
| 107 | +``` |
| 108 | +Status code 406 is not 400 |
| 109 | +``` |
| 110 | +17. SHOULD use 400 status code on number {variables} parameter when accepting application/graphql-response+json<br /> |
| 111 | +``` |
| 112 | +Status code 406 is not 400 |
| 113 | +``` |
| 114 | +18. SHOULD use 400 status code on boolean {variables} parameter when accepting application/graphql-response+json<br /> |
| 115 | +``` |
| 116 | +Status code 406 is not 400 |
| 117 | +``` |
| 118 | +19. SHOULD use 400 status code on array {variables} parameter when accepting application/graphql-response+json<br /> |
| 119 | +``` |
| 120 | +Status code 406 is not 400 |
| 121 | +``` |
| 122 | +20. SHOULD use 200 status code with errors field on string {variables} parameter when accepting application/json<br /> |
| 123 | +``` |
| 124 | +Status code 400 is not 200 |
| 125 | +``` |
| 126 | +21. SHOULD use 200 status code with errors field on number {variables} parameter when accepting application/json<br /> |
| 127 | +``` |
| 128 | +Status code 400 is not 200 |
| 129 | +``` |
| 130 | +22. SHOULD use 200 status code with errors field on boolean {variables} parameter when accepting application/json<br /> |
| 131 | +``` |
| 132 | +Status code 400 is not 200 |
| 133 | +``` |
| 134 | +23. SHOULD use 200 status code with errors field on array {variables} parameter when accepting application/json<br /> |
| 135 | +``` |
| 136 | +Execution result {"data":{"__typename":"Query"}} does not have a property 'errors' |
| 137 | +``` |
| 138 | +24. SHOULD allow map {variables} parameter when accepting application/graphql-response+json<br /> |
| 139 | +``` |
| 140 | +Status code 406 is not 200 |
| 141 | +``` |
| 142 | +25. MAY allow URL-encoded JSON string {variables} parameter in GETs when accepting application/graphql-response+json<br /> |
| 143 | +``` |
| 144 | +Status code 406 is not 200 |
| 145 | +``` |
| 146 | +26. MAY allow URL-encoded JSON string {variables} parameter in GETs when accepting application/json<br /> |
| 147 | +``` |
| 148 | +Execution result {"errors":[{"message":"Variable \"$name\" of required type \"String!\" was not provided.","locations":[{"line":1,"column":12}]}]} does have a property 'errors' |
| 149 | +``` |
| 150 | +27. SHOULD use 400 status code on string {extensions} parameter when accepting application/graphql-response+json<br /> |
| 151 | +``` |
| 152 | +Status code 406 is not 400 |
| 153 | +``` |
| 154 | +28. SHOULD use 400 status code on number {extensions} parameter when accepting application/graphql-response+json<br /> |
| 155 | +``` |
| 156 | +Status code 406 is not 400 |
| 157 | +``` |
| 158 | +29. SHOULD use 400 status code on boolean {extensions} parameter when accepting application/graphql-response+json<br /> |
| 159 | +``` |
| 160 | +Status code 406 is not 400 |
| 161 | +``` |
| 162 | +30. SHOULD use 400 status code on array {extensions} parameter when accepting application/graphql-response+json<br /> |
| 163 | +``` |
| 164 | +Status code 406 is not 400 |
| 165 | +``` |
| 166 | +31. SHOULD use 200 status code with errors field on string {extensions} parameter when accepting application/json<br /> |
| 167 | +``` |
| 168 | +Execution result {"data":{"__typename":"Query"}} does not have a property 'errors' |
| 169 | +``` |
| 170 | +32. SHOULD use 200 status code with errors field on number {extensions} parameter when accepting application/json<br /> |
| 171 | +``` |
| 172 | +Execution result {"data":{"__typename":"Query"}} does not have a property 'errors' |
| 173 | +``` |
| 174 | +33. SHOULD use 200 status code with errors field on boolean {extensions} parameter when accepting application/json<br /> |
| 175 | +``` |
| 176 | +Execution result {"data":{"__typename":"Query"}} does not have a property 'errors' |
| 177 | +``` |
| 178 | +34. SHOULD use 200 status code with errors field on array {extensions} parameter when accepting application/json<br /> |
| 179 | +``` |
| 180 | +Execution result {"data":{"__typename":"Query"}} does not have a property 'errors' |
| 181 | +``` |
| 182 | +35. SHOULD allow map {extensions} parameter when accepting application/graphql-response+json<br /> |
| 183 | +``` |
| 184 | +Status code 406 is not 200 |
| 185 | +``` |
| 186 | +36. SHOULD use 200 status code on JSON parsing failure when accepting application/json<br /> |
| 187 | +``` |
| 188 | +Status code 400 is not 200 |
| 189 | +``` |
| 190 | +37. SHOULD use 400 status code on JSON parsing failure when accepting application/graphql-response+json<br /> |
| 191 | +``` |
| 192 | +Status code 406 is not 400 |
| 193 | +``` |
| 194 | +38. SHOULD not contain the data entry on JSON parsing failure when accepting application/graphql-response+json<br /> |
| 195 | +``` |
| 196 | +Response body is not valid JSON. Got "Not Acceptable" |
| 197 | +``` |
| 198 | +39. SHOULD use 400 status code if parameters are invalid when accepting application/graphql-response+json<br /> |
| 199 | +``` |
| 200 | +Status code 406 is not 400 |
| 201 | +``` |
| 202 | +40. SHOULD not contain the data entry if parameters are invalid when accepting application/graphql-response+json<br /> |
| 203 | +``` |
| 204 | +Response body is not valid JSON. Got "Not Acceptable" |
| 205 | +``` |
| 206 | +41. SHOULD use 400 status code on document parsing failure when accepting application/graphql-response+json<br /> |
| 207 | +``` |
| 208 | +Status code 406 is not 400 |
| 209 | +``` |
| 210 | +42. SHOULD not contain the data entry on document parsing failure when accepting application/graphql-response+json<br /> |
| 211 | +``` |
| 212 | +Response body is not valid JSON. Got "Not Acceptable" |
| 213 | +``` |
| 214 | +43. SHOULD use 400 status code on document validation failure when accepting application/graphql-response+json<br /> |
| 215 | +``` |
| 216 | +Status code 406 is not 400 |
| 217 | +``` |
| 218 | +44. SHOULD not contain the data entry on document validation failure when accepting application/graphql-response+json<br /> |
| 219 | +``` |
| 220 | +Response body is not valid JSON. Got "Not Acceptable" |
| 221 | +``` |
| 222 | + |
| 223 | +## Errors |
| 224 | +The server _MUST_ support these. |
| 225 | +1. MUST use utf-8 encoding when responding<br /> |
| 226 | +``` |
| 227 | +Body is not UTF-8 encoded |
| 228 | +``` |
| 229 | +2. MUST accept utf-8 encoding<br /> |
| 230 | +``` |
| 231 | +Content-Type header "application/json" does not contain "utf-8" |
| 232 | +``` |
| 233 | +3. MUST assume utf-8 if encoding is unspecified<br /> |
| 234 | +``` |
| 235 | +Content-Type header "application/json" does not contain "utf-8" |
| 236 | +``` |
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?v=4&size=40){kind=avatar}
0 commit comments