{"message":"Invalid "Content-Range" provided"} when uploading tracks

[stormsnsnow]

Short Information

• Used Toolkit version: 3.0.5
• Operating System: Windows 11 24H2

Problem Definition Briefly (might be explained in steps)

• When uploading tracks captured with KV, an error appears when going to 143/1000.
• {"message":"Invalid "Content-Range" provided"}
• Appears when uploading large tracks.

Expected Output

• Upload complete without errors.

Actual Output

• {"message":"Invalid "Content-Range" provided"}

Extra information (can contain screen shots)

[chrisdebian]

Hi,

The root cause is a bug in mapilio-kit's upload loop — the header was being sent incorrectly.

RFC 7233 requires:

Content-Range: bytes <start>-<end>/<total>

where <end> is the last byte of the current chunk (0-indexed, inclusive). The code was sending <end> as the total file size instead, making every intermediate chunk's range invalid. Uploads fitting in a single chunk (< 64 MB) would not trigger this because there is only one chunk.

Fix: mapilio/mapilio-kit#212 — corrects the header and adds unit tests.

Please upgrade mapilio-kit once that PR is merged, or watch that PR for the release.

Thanks, Chris