Skip to content

feat: complete the GraphQL server HTTP binding (G1) #1590

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jlouvel merged 3 commits into from
Nov 1, 2026
Merged

feat: complete the GraphQL server HTTP binding (G1) #1590

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
44144e2
feat: complete the GraphQL server HTTP binding (G1)
jlouvel Oct 30, 2026
35514e6
test: tolerate an early 413 on chunked GraphQL requests
jlouvel Oct 30, 2026
a923c1e
fix: check the customized GraphQL operation and refine GET responses
jlouvel Oct 30, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion changes.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -140,7 +140,11 @@ Changes log
GraphQL over HTTP draft (`application/graphql-response+json` and `application/json`);
operations run on the call's virtual thread. `GraphqlClientAdapter` sends operations
through a borrowed `Client` and returns native `ExecutionResult` values, throwing
`GraphqlTransportException` when no GraphQL response is received. Issue #1581.
`GraphqlTransportException` when no GraphQL response is received. The server accepts
queries over `GET` when enabled (off by default), applies the draft's status codes per
response media type, limits the request size (1 MiB by default) and the parser per
adapter (`ParserOptions`, never the process-wide defaults), and gives data fetchers the
Restlet request and client info through `RestletGraphql` context keys. Issue #1581.
- Added the `NettyConnectionUpgrade` engine hook: a Restlet returning a "101 Switching
Protocols" response with this response attribute takes over the HTTP/1.1 connection
(`NettyUpgradeContext`), which the WebSocket extension relies on.
Expand Down
Loading
Loading