Works with the AI tools you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIGitHub CopilotGitHub CopilotGemini CLIGemini CLI+17 more

    Repair Range Request Corruption

    1

    Repair HTTP byte-range bugs that return wrong offsets, corrupt resumable downloads, mishandle suffix or open-ended ranges, combine incompatible validators, or emit invalid 206/416 responses.

    Secure checkout via Stripe

    0 installsSecurity scanned

    See it in action

    You say

    Repair our Go download handler. A resumed request bytes=1048576- starts one byte late, suffix ranges fail on small files, and If-Range is checked after opening the partial stream. Use local byte fixtures. Preserve authorization, storage abstraction, ETag policy, compression, retries, and errors.

    Your agent does

    Range-contract defect found. The parser converts inclusive HTTP bounds into half-open storage offsets twice, causing an off-by-one resume gap, and suffix handling underflows below zero. The repair creates one canonical interval conversion, checks If-Range before partial delivery, preserves authorization/storage/compression/retry policy, and verifies 200, 206, 416, suffix, open-ended, multipart, and changed-validator cases byte for byte.

    What you get

    Resolve byte-level corruption in resumable file downloads.Align Content-Range headers with actual payload byte counts.Fix If-Range validator gates to prevent serving stale representation data.Standardize inclusive interval math across parsing and framing layers.

    About this skill

    The problem

    Resumable downloads fail when byte offsets are off-by-one or range headers disagree with the actual payload. These bugs are notoriously difficult to debug, often resulting in corrupted files, duplicated data, or incorrect 206 Partial Content responses.

    What it does

    • Analyzes Range and Content-Range parsing logic to identify inclusive interval math errors.
    • Fixes suffix, open-ended, and multipart range calculations that lead to boundary byte corruption.
    • Ensures If-Range validators correctly prevent serving stale bytes from modified representations.
    • Standardizes response framing to align headers with actual payload lengths.
    • Generates deterministic local fixtures to reproduce and verify fixes without production access.

    Why this beats prompting it yourself

    General LLMs often struggle with the precise 0-indexed vs 1-indexed math required for HTTP range requests and frequently suggest "fixes" that break multipart compliance. This skill enforces a strict ownership and normalization register, ensuring that authorization and cache policies remain untouched while the underlying byte math is repaired.

    Use cases

    • Fixing corrupted file downloads where the first or last bytes are missing.
    • Correcting 416 Requested Range Not Satisfiable errors on valid files.
    • Repairing multipart range responses where boundaries are incorrectly merged.
    • Synchronizing compressed offsets with uncompressed file bounds.

    Known limitations

    Does not modify authorization logic, storage drivers, or external retry policies. Requires local repository files to function and cannot test against live production endpoints.

    How to install

    Drop the file into your AI Agent. Works with Claude, Cursor, ChatGPT, and 20+ more.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill passes our trust checks below.

    Security scanned

    Passed our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    30-day refund

    Not a fit? Get your money back

    Trust & safety

    Security scanned

    Verified clean today

    • One-time purchase, yours forever

    Listedtoday

    Frequently Asked Questions