[bug] asset protocol multi-range responses: missing close delimiter, duplicate Content-Type, and 200 instead of 206

Important limitations

• This may be one public report, not widespread demand.
• Current independent report count: 1.
• This is currently a single independent report. It has not passed clustering or human review as a verified signal.
• No market size, willingness to pay, competition, or trend claims are inferred here.

What was reported

Who is affected

Application developer using the reported software

Job to be done

Run tests reliably

Workflow

I hit these from a unit test rather than an app, so instead of a repro repo here is the observed output — a 1000-byte file requested with `Range: bytes=0-9, 20-29` through `protocol::asset::get(..)` on `dev`:

Desired outcome

A multi-range request should return `206 Partial Content`, exactly one `Content-Type: multipart/byteranges; boundary=...`, and a body terminated with `\r\n--{boundary}--\r\n`.

Severity

Not enough evidence yet.

Urgency

Not enough evidence yet.

Evidence indicators

What would upgrade this

• Additional independent reports from distinct communities or authors.
• Human clustering into a review signal, then explicit publication approval.
• Counter-evidence review and durable original-source verification.

Original source

Open the original public report