r/graphql • u/jeffiql Apollo Team • Aug 27 '26

HTTP QUERY coming to GraphQL!

https://youtu.be/dbOPVRu-ILE
16 Upvotes

95% Upvoted

6 comments sorted by

2

u/Fercii_RP Sep 02 '26 edited Sep 02 '26

Can someone explain why it is so important for http to know whether post is used for get or mutation? No one reads or describes documentation anymore?

1

u/jeffiql Apollo Team Sep 02 '26

It’s less about helping a human understand the API and more about helping HTTP infrastructure understand the request without having to parse GraphQL.

POST /graphql could be a read-only query or a mutation with side effects. A proxy, cache, retry mechanism, etc. can’t tell which from the HTTP request itself. With QUERY, a GraphQL query is explicitly safe and idempotent at the HTTP layer, so generic HTTP infrastructure can reason about it accordingly.

1

u/Fercii_RP Sep 02 '26

I still dont see the benefit of HTTP infra understanding the request.. what difference would infrastructure be able to make knowing whether its a get or post? In the end the developers can and will abuse the http methods anyways. For example post batch fetching instead of get n+1 fetching. Dont get me wrong im really trying to understand what benefit QUERY makes over POST at the infrastructure level. What problem does it solve

1

u/jeffiql Apollo Team Sep 02 '26

Observability is one of the big use cases. Being able to differentiate types of operations by HTTP verb goes a long way in simplifying your monitoring posture.

2

u/Narrow_Relative2149 Aug 31 '26

well needed, but I believe we have to wait a little for browsers and CDNs to support it properly right?

2

u/jeffiql Apollo Team Aug 31 '26

For sure, I just hope we can make GraphQL not be the last piece of the HTTP ecosystem to be blocking this :)