{
  "schema_version": "1.3.0",
  "slug": "under-what-conditions-must-an-instance-refuse-to-resume-an-mcp-session-across-an-http-native-transport-upgrade",
  "title": "Under what conditions must an instance refuse to resume an MCP session across an HTTP-native transport upgrade",
  "date_of_record": "2026 November 17",
  "scope": "Applies to MCP servers exposing both the legacy HTTP+SSE transport and the streamable-HTTP transport on the same host, where session continuity is attempted via `Last-Event-ID` replay and the caller is authorized under an OAuth 2.1 resource-server binding with a token audience scoped to a single transport endpoint. Does not apply to pure stdio transports, nor to deployments where the authorization server issues audience-agnostic tokens.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-refuse-to-resume-an-mcp-session-across-an-http-native-transport-upgrade.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-refuse-to-resume-an-mcp-session-across-an-http-native-transport-upgrade.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-refuse-to-resume-an-mcp-session-across-an-http-native-transport-upgrade.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1393,
    "python_slice_tokens": 221,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "Session identity and transport identity are orthogonal, but the resumption path in HTTP-native MCP conflates them. A session is a logical conversation keyed by `Mcp-Session-Id`; a transport is the wire binding that carries it. The SSE transport encodes resumption state as an event-ID cursor (`Last-Event-ID`) replayed against a per-connection event log. Strea...",
    "what_was_observed": "A client opened an SSE session, received `Mcp-Session-Id: S1` and a stream of events carrying monotonically increasing IDs `e1…e42`. The SSE connection dropped at `e42`. The client, upgraded to streamable HTTP (same host, same path prefix, different `Accept` negotiation), issued `POST` with `Mcp-Session-Id: S1` and `Last-Event-ID: e42`. The server accepted the request, found session `S1` in its store (the ID namespac...",
    "condition_of_validity": "Cross-transport resumption is safe **only** when all three of the following hold simultaneously: 1. The session store records the transport binding (`transport: \"sse\" | \"streamable-http\"`) at session creation and rejects resume attempts whose presented transport differs, returning a terminal `404`/`400` rather than a best-effort replay. 2. The `Last-Event-ID...",
    "decision_boundary": "The decision to refuse is not \"should I resume?\" but \"is the presented resume cursor provably from the same event log as the session's current transport binding?\" If the session's recorded transport differs from the request's transport, refuse unconditionally — do not attempt cursor translation, do not fall back to replay-from-zero, do not silently re-initia...",
    "operational_effect": "Enforcing the boundary converts a silent data-integrity failure into a loud, recoverable protocol error. Clients see a `400` on resume, discard local session state, and re-run `initialize` — adding one round trip but preserving the event-sequence invariant. The OAuth audience check moves from \"valid token for this server\" to \"valid token for this endpoint,\" ..."
  },
  "matched_failure_symptoms": [
    "DOMAIN:EPISTEMIC_PROVENANCE_AND_FEDERATION_ROUTING"
  ],
  "composition_edges": {
    "primary_domain": "epistemic_provenance_and_federation_routing",
    "upstream_precondition_residuals": [
      "https://corpusfetch.com/c/according-to-what-precedence-hierarchy-must-an-instance-resolve-contradictory-directives-across-system-developer-and-user-tiers.md",
      "https://corpusfetch.com/c/how-should-an-instance-decide-that-a-stored-conclusion-has-gone-stale-without-a-new-observation.md"
    ],
    "downstream_consequence_residuals": [
      "https://corpusfetch.com/c/by-what-checkpoint-and-compaction-boundaries-must-an-instance-externalize-working-state-to-prevent-context-window-drift-and-truncation-amnesia.md",
      "https://corpusfetch.com/c/across-what-additive-schema-and-unknown-field-preservation-boundaries-must-an-instance-evolve-wire-contracts-to-prevent-rolling-deploy-deserialization-crashes.md"
    ],
    "co_occurring_sibling_residuals": [
      "https://corpusfetch.com/c/how-can-an-instance-capture-implicit-user-preferences-without-storing-private-data.md",
      "https://corpusfetch.com/c/how-can-an-instance-compress-long-reasoning-traces-into-binding-conclusions.md"
    ]
  },
  "empirical_verification_warrant": {
    "status": "AST_AND_INVARIANT_VERIFIED",
    "syntax_valid": true,
    "code_sha256": "cc5572d94814862084d4d3ed790e432ca7268b88e3018b1211dd11ff61092906",
    "verified_classes": [
      "CrossTransportResumeError"
    ],
    "verified_functions": [
      "resume_session"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 5,
    "raised_exceptions": [
      "CrossTransportResumeError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
