Lies about gzip encoding

broken-gzip · Status & reliability

Endpoint (Streamable HTTP)

https://chaos-mcp.thomascdnns.com/s/broken-gzip/mcp

On the wire — recorded from a real request

Symptom

what you'll observe

Client errors with 'invalid gzip header' / decompression failure.

Cause

what this reproduces

Content-Encoding: gzip is set but the body is plain text (double-encoding middleware bug).

Fix

how you'd resolve it

Only set Content-Encoding when you actually compressed; let the framework manage it.

Try it with curl

bash

curl -sS -X POST \
  https://chaos-mcp.thomascdnns.com/s/broken-gzip/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json' \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "initialize",
    "params": {
      "protocolVersion": "2024-11-05",
      "capabilities": {},
      "clientInfo": {"name": "curl", "version": "1"}
    }
  }'