Spec gap: no defined success response for session-termination DELETE (only 405 is specified)
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 30/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- typescript
- Domain
- documentation
Research direction
Start with the Streamable HTTP DELETE behavior described in the issue and review #322's server-session-lifecycle scenario. Compare the current WARNING handling for non-2xx/405 and 404 already-terminated cases with the clarification expected from the modelcontextprotocol spec repo. Done means the external spec defines the success status and 404 semantics, after which #322 can be tightened.
Written by the indexing model from the issue text.
Description
Problem
The Streamable HTTP transport spec says clients SHOULD send an HTTP DELETE to terminate a session and servers MAY respond 405 if they don't allow client-initiated termination. It never states what a successful termination response looks like (200? 204? any 2xx?), nor whether 404 is acceptable for a session that is already gone.
This bit us while reviewing #322 (server-session-lifecycle scenario): with no spec anchor, any strict status assertion invents a requirement. The scenario currently treats non-2xx/405 as WARNING rather than FAILURE, and 404 as already-terminated, but that's a harness judgment call, not spec.
Ask
Track here for now; this should become a clarification issue/PR on the spec repo (modelcontextprotocol) pinning the expected success status family for DELETE, and the semantics of 404 on an already-terminated session. Once the spec answers, tighten the #322 checks to match.
- Dominant language
- TypeScript
- Stars
- 127
- Forks
- 101
- Avg merge
- 4d 7h
- Merged PRs (30d)
- 6
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from modelcontextprotocol/conformance
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
modelcontextprotocol/conformance#315 · 1 comment ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
modelcontextprotocol/conformance#312 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
-
Difficulty 4/5 3-5 days Newbie friendliness 40/100
-
Difficulty 3/5 1-2 days Newbie friendliness 65/100
All issues in modelcontextprotocol/conformance
Similar issues
-
VerificationGate: ATTRIBUTION quote guard never matches a normal quotation (\b around the quote) Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
danielmiessler/LifeOS#2234 ·
-
T: Bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
Mend: dependency security vulnerability untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 70/100