Skip to content

Fix request-metadata handling of empty HTTP probes#409

Draft
tsarlandie-oai wants to merge 1 commit into
modelcontextprotocol:mainfrom
tsarlandie-oai:codex/request-metadata-empty-get
Draft

Fix request-metadata handling of empty HTTP probes#409
tsarlandie-oai wants to merge 1 commit into
modelcontextprotocol:mainfrom
tsarlandie-oai:codex/request-metadata-empty-get

Conversation

@tsarlandie-oai

Copy link
Copy Markdown

Summary

  • reject unsupported HTTP methods before parsing a JSON-RPC body in the
    request-metadata client scenario
  • return a structured JSON-RPC parse error for malformed POST bodies
  • cover empty-body GET/DELETE probes and malformed POST requests with
    regression tests

This prevents a valid Streamable HTTP endpoint probe from crashing the entire
conformance runner with SyntaxError: Unexpected end of JSON input.

Fixes #408.

Validation

  • npm test (440 tests passed)
  • npm run typecheck
  • npm run lint
  • npm run build
  • exercised the scenario with a real Codex HTTP client; the adapter completed
    discovery and the runner emitted checks instead of crashing

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

request-metadata client scenario crashes on empty-body GET

1 participant