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
{{ message }}
This repository has been archived by the owner on Apr 14, 2023. It is now read-only.
I don't want to open yet another discussion regarding HTTP GET vs POST for GraphQL queries, but I wonder if there is way today to customise the HTTP method per-query?
I wish to set the useGETForQueries flag to true by default in order to take advantage of HTTP caching.
However, I run the API on AWS API Gateway which introduces hard HTTP limitations, especially on the queryString:
max 8192 characters for edge-optimised APIs
max 10240 characters for regional APIs
In my current project, it happens that some queries reach those limitations, and API Gateway started to returns 413 Payload Too Large errors
I would find it useful to have an option to override the HTTP method for specific queries, for instance in the query options?
const{ error, loading, data }=useQuery(SOME_TOO_LONG_QUERY_FOR_GET,{httpMethod: 'POST'});
Not sure if that makes sense or if other ways could be better?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I don't want to open yet another discussion regarding HTTP
GET
vsPOST
for GraphQL queries, but I wonder if there is way today to customise the HTTP method per-query?I wish to set the
useGETForQueries
flag totrue
by default in order to take advantage of HTTP caching.However, I run the API on AWS API Gateway which introduces hard HTTP limitations, especially on the queryString:
In my current project, it happens that some queries reach those limitations, and API Gateway started to returns
413 Payload Too Large
errorsI would find it useful to have an option to override the HTTP method for specific queries, for instance in the query options?
Not sure if that makes sense or if other ways could be better?
The text was updated successfully, but these errors were encountered: