docs: add explanation about GET Vs POST queries #99
Conversation
|
@theodesp LGTM 🚀 Should we include anything about caching too. Would there be a reason why someone might use GET over POST (or visa versa) in relation to caching? |
theodesp
changed the title
There was a problem hiding this comment.
Good work. Let's add a brief section on [Automatic] Persisted Queries and how APQs solve the issues with GET requests with links out to Apollo docs or the GraphQL spec (if there is one) where folks can get more info. a link to the how-to could be good too.
|
|
||
| Each property is provided as an HTTP query parameter, with values separated by an ampersand (&). | ||
|
|
||
| GraphQL requests with variables don't work in GET requests because they need to be parsed as JSON. |
There was a problem hiding this comment.
This is not true:
https://graphql-cache.local/graphql?query=query($slug:ID!){post(id:$slug,idType:SLUG,asPreview:false){title,content}}&variables={%22slug%22:%22hello-world%22}
| | Method | Security | Complexity | Support | Use Case | | ||
| |--------------------------|------------------------------------------|-----------------|------------|------------------------| | ||
| | POST | More secure, hides query in request body | Complex queries | Production | complex data retrieval | | ||
| | GET with Query Parameter | Less secure due to query exposure in URL | Simple queries (no mutations) | Testing | simple data retrieval | |
There was a problem hiding this comment.
HTTPS secures URL information only domain is exposed due to DNS and TLS being established. see: https://stackoverflow.com/a/499594
Co-authored-by: Alex Moon <moonmeister@users.noreply.github.com>
Co-authored-by: Alex Moon <moonmeister@users.noreply.github.com>
#53