-
Notifications
You must be signed in to change notification settings - Fork 353
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
APQ seems to be partially implemented in Spring Server #2065
Comments
For info, I could make it work by overriding the default SpringGraphQLRequestParser as follows:
Notice the 'extensions' field is also not mapped in the standard class, which causes further problems with invalid query parsing afterwards. I checked the Ktor server project, and it seems to have the same issue. |
the issue is with the GraphQLRequestParser specifically for GET requests, it was never implemented. if you can use POST, ill try to make some time to work on it, but it you prefer, contributions are always welcomed. |
Great! I'll try submitting a PR when I get it done. Thanks for the fast reply. |
Hello @samuelAndalon. For info, I submitted a PR here. |
… hash of query string (#2067) ### 📝 Description According to the GraphQL APQ flow description, GET requests containing only SHA-256 hash of the query should be checked in cache and respond with PERSISTED_QUERY_NOT_FOUND error if request is not cached. Both Ktor and Spring server implementations didn't handle this first query without a query param. I tried to implement the change without breaking existing behaviours, as a query param is expected to take precedence over post body, for example, as in one of the tests in RouteConfigurationIT. ### 🔗 Related Issues #2065
Library Version
8.2.1
Describe the bug
We tried to enable APQ in spring server, which according to the documentation requires only setting
automaticPersistedQueries.enabled: true
, but unfortunately the APQ flow doesn't work as expected because the initial GET call fail in GraphQLServer with bad request without a body (I'd expect a PersistedQueryNotFound error be available in the payload, for eg). The AutomaticPersistedQueriesProvider is not even executed.The request fails because the parseRequest returns null (no query parameter available):
and therefore the router returns bad request here (GraphQLRoutesConfiguration):
To Reproduce
We first tried it with Apollo Client and our own requests and saw the router not being able to resolve the request with 400s, and then we tried to reproduce it with simple examples from Apollo as described below:
1st GET request without query returns 400:
2nd GET request with query returns 200:
Send another GET request without the query and the cache is still not checked and we still receive 400:
Expected behavior
The first call should not fail with bad request, and it should be able to resolve from cache after the result is properly cached.
Also, from the client implementation that's how it's supposed work (first request without a "query" parameter):
graphql-kotlin/clients/graphql-kotlin-spring-client/src/main/kotlin/com/expediagroup/graphql/client/spring/GraphQLWebClient.kt
Line 69 in 681c70d
The text was updated successfully, but these errors were encountered: