gabriel / muse public
fix BREAKING task/fix-fetch-content-type #1 / 1
AI Agent gabriel · 44 days ago · Apr 28, 2026 · Diff

fix: fetch_stream sends Content-Type x-msgpack, Accept x-muse-wire

The fetch request body is a fixed-size msgpack dict — not a streaming wire frame. Setting Content-Type: x-muse-wire caused the server to verify the MSign signature against SHA256("") (the streaming-push convention) while the client signed against SHA256(body). Guaranteed 401 on muse pull.

Remove Content-Type from extra_headers so _build_request uses its default application/x-msgpack. Keep Accept: x-muse-wire — the response IS a wire frame stream.

sha256:8b6365d66de1603a3c34d2c1393832181219a8b94c24187e80ada19848e25880 sha
sha256:d811ab4279347af502829093b6ee850511d5e29d79bacd3887797745b486e329 parent
sha256:7cad168ea223800b1eb1f3a34598a1ada9516766e941f274ebb4267fb9898f0c snapshot
← Older Oldest on task/fix-fetch-content-type
All commits
Newer → Latest on task/fix-fetch-content-type

0 comments

No comments yet. Be the first to start the discussion.

To add a comment, use the Muse CLI: muse hub commit comment sha256:8b6365d66de1603a3c34d2c1393832181219a8b94c24187e80ada19848e25880 --body "your comment"