HTTP Router Provide Bug Repro

Minimal repo that shows routing provide (and fast-provide after ipfs add) does not send provider records to an HTTP router on recent Kubo versions.

Prereqs

• Node 18+ (repo uses the npm kubo binary)

Quick start

npm install
npm run repro

What the script does:

1. Starts a mock HTTP router on 127.0.0.1:19575 that records all requests.
2. Inits a fresh Kubo repo with randomized ports and Routing.* pointing to the mock router (MDNS off).
3. Starts ipfs daemon.
4. Adds a test file with ipfs add (--fast-provide-wait if supported).
5. Calls ipfs routing provide --recursive --verbose <cid> <raw-mh-cid>.
6. Prints every request seen by the mock router, then shuts everything down. The checks look for the added CID in three forms: dag-pb (v0), v1, and raw/0x55 multihash.

Expected vs actual

• Kubo 0.39.0: no requests reach the HTTP router (empty log).
• Kubo 0.38.0: PUTs arrive but do not contain the added CID.
• Kubo 0.37.0: ipfs add sends PUTs that include the CID; explicit routing provide fails with “cannot provide, no connected peers” because the node is isolated.

Switching versions

Update the dependency and rerun:

npm install [email protected]   # or 0.38.0, 0.37.0
npm run repro

Filing upstream

ISSUE.md contains a prefilled GitHub issue template; replace <url> with this repo’s URL when filing.***