You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[spring-server] fix: correctly handle graphql request with charset encoding (ExpediaGroup#425)
In our default GraphQL route we were explicitly checking if `Content-Type` header is just `application/json`. If request was also specifying charset, e.g. `application/json;charset=UTF-8` our logic would fail to match it and result in HTTP 400 (Bad Request) response.
Copy file name to clipboardExpand all lines: graphql-kotlin-spring-server/src/test/kotlin/com/expediagroup/graphql/spring/routes/RouteConfigurationIT.kt
+17Lines changed: 17 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -215,6 +215,23 @@ directive @deprecated(reason: String = "No longer supported") on FIELD_DEFINITIO
215
215
.jsonPath("$.extensions").doesNotExist()
216
216
}
217
217
218
+
@Test
219
+
fun`verify POST graphQL request with explicit charset`() {
0 commit comments