ToolJovia
Developer

HTTP Byte Range Workbench

Resolve Range fields against an explicit representation length or inspect a Content-Range field with exact integers.

✓ Browser-local processing

Loading tool…

How to use HTTP Byte Range Workbench

Resolve Range fields against an explicit representation length or inspect a Content-Range field with exact integers. Inspect open-ended, suffix, clipped and unsatisfied ranges. Optional coalescing sorts and merges adjacent/overlapping selections without allocating any representation bytes.

  1. Provide range or content-range field value, representation length in bytes.
  2. Choose the supported mode and run the tool. Review its assumptions and any reported errors.
  3. Copy the result or download a separate output; reset to clear the current form.

Good to know

  • 100 ranges, a 10 KB header and exact unsigned integers through 2^63−1. Canonical decimal input is required. Only the bytes unit is supported.
  • Length applies to the selected representation, including content encoding when applicable. No files, HTTP request, response body or multipart body is fetched/generated.
  • Coalesced totals count each merged byte once; totals in keep mode count repeated/overlapping selections repeatedly. A valid numeric range is not a promise that a server accepts it.
  • Inputs are processed on this device and are not automatically saved or uploaded.

Common questions

What does a suffix range such as -20 select?

For a nonempty representation, it selects its final 20 bytes or the entire representation when it is shorter. A zero-length suffix selects nothing. A nonzero suffix on an empty representation is satisfiable under RFC 9110 even though it selects zero bytes.

Does this change my original input?

No. The tool returns a separate result. Review that output before using it in another application.

Keep going with related tools

All developer →