The configured response cache, or undefined when the
request runs cache-less (the default).
The HTTP method.
The request body, when present.
Whether the call resolved to the REST protocol; REST
POST bodies are never treated as GraphQL query documents even when a
body field is named query.
The resolved auth facts of the request.
The cache key fragment, or undefined to skip the cache.
Computes the auth-scoping cache key for a cacheable request, or
undefinedwhen the request must not touch the cache.The cache applies only to cacheable reads with a configured cache:
GETcalls, and GraphQL query documents dispatched asPOST(the AniList transport's only read shape: every GraphQL operation is a POST, so aGET-only gate would leave the cache inert for the primary provider). Mutations, GraphQLmutationdocuments and RESTPOST/PUT/DELETEcalls, stay excluded. When effective credential headers are present but not captured by the cache key (for example a customAuthorizationorX-API-Keyheader), buildCacheAuthKey returnsundefinedto fail closed: the cache is skipped entirely instead of risking a cross-identity disclosure.