Serve GraphQL subscriptions only over HTTP multipart responses
Amends ADR-0041: no WebSocket endpoint serves the subscription resolvers.
Decision
Serve every GraphQL operation, subscriptions included, through the one HTTP endpoint. A subscription is a multipart HTTP response, which Apollo iOS supports. Offer no WebSocket transport for GraphQL, and keep a test that a WebSocket upgrade request is refused.
Why
The WebSocket endpoint ran queries and mutations as well as subscriptions, and it ran them outside the request limits the HTTP layer applies to every other call. Each limit would have needed a second enforcement point on a transport no client used: the app subscribes over multipart HTTP and MCP clients have their own endpoint.
Rejected alternatives
- Keep the WebSocket endpoint and apply the same limits there. Every future limit would have to be added on both transports, and a limit missing from the WebSocket path would go unnoticed because no client uses it.
Consequences
A client that subscribes only over the graphql-ws protocol, as many web GraphQL clients do by default, must use multipart HTTP instead. Adding a WebSocket transport back means first routing it through the same limits as HTTP.