wtf is graphql-over-http?

GraphQL is a popular query language for APIs that lets clients ask for exactly the data they need. The core GraphQL specification defines how queries are written and executed, but it deliberately leaves out the rules for how that data actually travels across the internet. In practice, most teams send GraphQL queries over HTTP, the standard protocol of the web. The graphql-over-http repository exists to create a formal, written specification for how GraphQL should be served over HTTP, replacing the informal best practices that currently exist. Today, the way GraphQL works over HTTP is governed mostly by convention. An older article on the GraphQL website outlined some basic best practices, and the most popular client and server libraries followed those conventions. This created a working but unofficial standard across the industry. The project aims to turn those widely-adopted conventions into a rigorous, official specification. The main goal is to ensure interoperability, so that any GraphQL client can talk to any GraphQL server without running into unexpected compatibility issues. This repository is primarily for the people who build GraphQL tools, such as the developers creating client libraries, server frameworks, and testing utilities. Before this specification, a tool builder might have to guess at edge-case behavior or rely on undocumented norms. With a formal spec in place, they have a single source of truth to code against. For a product manager or founder building an application that relies on GraphQL, the practical benefit is a healthier ecosystem where different tools and services plug together more reliably, reducing the risk of vendor lock-in or integration headaches. The project is currently in the draft stage, meaning the specification is still being actively developed and could change before it is officially accepted. The repository itself functions as the workspace for this collaborative writing effort. Contributors from the community can propose changes, though the project requires participants to sign a free membership agreement before they can contribute code or text. The community coordinates this work through a dedicated channel on the GraphQL Foundation's Discord server.