Security

Public GraphQL sits on POST (plus optional streams). Prefer HTTPS, reverse-proxy rate limits, and Authorization/session middleware terminating before GraphQL unmarshals payloads.

Prefer grx.NewServer With* helpers; fields only on [server.Config](https://pkg.go.dev/github.com/grx-gql/grx/server#Config) require server.New (**same http.Handler ergonomics grx.NewServer uses internally).

Companion guides:

• Introspection
• Limits
• Deployment (containers, proxies, Kubernetes)

Mask internal errorsCopy Anchor Link

Resolver/driver panics leaking raw strings into errors[].message is risky. MaskInternalErrors on server.Config collapses internals to ClientErrorMessage (or the default string) while plugin hooks still observe the original error.

package main

import (
	"log"

	"example.com/hello-grx/graph"

	"github.com/grx-gql/grx/server"
)

func main() {
	srv, err := server.New(server.Config{
		Schema:             graph.Schema(),
		MaskInternalErrors: true,
		ClientErrorMessage: "internal error", // omit for default wording
	})
	if err != nil {
		log.Fatal(err)
	}
	_ = srv
}

Discuss partial success styling in Errors & client responses.

Authorization at the GraphQL boundaryCopy Anchor Link

Layer grx.WithOperationAuthorizer (parsed document gate) plus WithFieldAuthorizer (fine-grained per selection) atop HTTP identity - details + Bearer samples in Auth guide.

server.Config.RateLimiter hooks **exec.RateLimiter** implementations that reject workloads before resolver execution (still after lexical parse unless you choke earlier middleware).

Checklist snapshotCopy Anchor Link