Method Contexts
Method context pages explain how each HTTP method carries the actual elicitation techniques and which RFC-defined differentials are reachable through that method.
Method context pages explain how each HTTP method carries the actual elicitation techniques and which RFC-defined differentials are reachable through that method. The method is the transport frame; the existence signal comes from the attached technique.
This section covers two method contexts:
GET— the primary and broadest carrier method. Supports validator retrieval, range evaluation, precondition evaluation, and negotiation. The only RFC-defined method context for range handling.HEAD— a narrower mirror ofGETthat suppresses response content. Valid for conditional retrieval and precondition evaluation, but not a core range carrier.
Key principle: Neither method is itself the elicitation technique. Plain GET or HEAD without a Stage 2 manipulator is baseline transport context, not the oracle result.
Accept-Charset
Accept-Charset lets the client express which character encodings are acceptable in a textual response — structurally valid but weak, deprecated in RFC 9110.
GET — Method Context
GET is the primary retrieval method context that carries validator, precondition, and range request modifiers for existence oracle analysis.