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
Is your feature request related to a problem? Please describe.
Our backend (Magento) is using Varnish/Fastly as a caching layer for GraphQL. This works fine, but only for GET requests. When building new shops, we regularly run into max URL lengths (8000 characters as defined by the spec https://www.rfc-editor.org/rfc/rfc9110#section-4.1-5)
Describe the solution you'd like
We'd to be able to configure useAQP: true on a GraphQL handler. So that the it communicates with the AQP protocol.
And an additional benefit would be that this, would reduce network overhead.
Describe alternatives you've considered
We've been following the strategy to keep the query size down as much as possible. But it has been a continuous struggle and we keep hitting limits when a frontend developer does something a little bit more than query a few fields.
Additional context
This came to our attention again when we ran into #7235 and with sufficiently complex backends users run into
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Our backend (Magento) is using Varnish/Fastly as a caching layer for GraphQL. This works fine, but only for GET requests. When building new shops, we regularly run into max URL lengths (8000 characters as defined by the spec https://www.rfc-editor.org/rfc/rfc9110#section-4.1-5)
Describe the solution you'd like
We'd to be able to configure
useAQP: true
on a GraphQL handler. So that the it communicates with the AQP protocol.And an additional benefit would be that this, would reduce network overhead.
Describe alternatives you've considered
We've been following the strategy to keep the query size down as much as possible. But it has been a continuous struggle and we keep hitting limits when a frontend developer does something a little bit more than query a few fields.
Additional context
This came to our attention again when we ran into #7235 and with sufficiently complex backends users run into
The text was updated successfully, but these errors were encountered: