The GraphQL Technical Steering Committee announced the first release of the GraphQL over HTTP specification, addressing long-standing interoperability and observability issues for the transport-agnostic GraphQL spec. A key improvement introduces a new application/graphql-response+json media type to replace the problematic convention of returning 200 status codes for all GraphQL responses, enabling better differentiation between valid responses and proxy/cache errors.
Background
GraphQL was first released in 2015 as a query language specification that is intentionally transport-agnostic, leaving implementation details like HTTP handling to developers. This has led to inconsistent practices across the ecosystem, particularly around error handling and HTTP semantics.
- Source
- Lobsters
- Published
- Nov 13, 2026 at 09:16 AM
- Score
- 8.0 / 10