test: pin authenticated GET/DELETE on /mcp returning 405
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 157
- Forks
- 32
- Avg merge
- 1h 25m
- Merged PRs (30d)
- 145
Description
Follow-up from the protocol-version docs audit: the sessionless /mcp serving posture means GET and DELETE return 405 after authentication (rmcp 3.1.2 tower.rs serves POST-only when legacy_session_mode = false with no event store), and the docs now state this — but no first-party test in this repo pins it. The guarantee currently rests on the vendored SDK's dispatch arm alone; an rmcp upgrade that starts serving GET (SSE streams) or DELETE (session teardown) by default would change the wire surface silently.
Add a small case to crates/aisix-mcp/tests/protocol_generations.rs (or the proxy suite for the authenticated path): authenticated GET /mcp and DELETE /mcp → 405, unauthenticated → 401 first.
🤖 Generated with Claude Code
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.
Research direction
Start in crates/aisix-mcp/tests/protocol_generations.rs and inspect the existing authenticated protocol cases; the issue also identifies the proxy suite as an alternative. Add coverage for GET and DELETE on /mcp, verifying authenticated requests return 405 and unauthenticated requests return 401 first; done means these responses are pinned by a first-party test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, testing
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 84/100