[tejgokani]

Problem

ctx.request.length uses ~~len (double bitwise NOT) to parse the Content-Length header, which truncates values to a signed 32-bit integer. For Content-Length values exceeding 2,147,483,647 bytes (~2GB), the result silently wraps to incorrect values:

~~'2147483648'  → -2147483648  (sign flip)
~~'4294967296'  → 0
~~'10000000000' → 1410065408   (garbage)

This affects any middleware using ctx.request.length for upload size enforcement, rate limiting, or request body pre-allocation. In the era of large file uploads and video processing APIs, this is a realistic scenario.

Solution

Replace ~~len with Number.parseInt(len, 10):

• Replace ~~len (32-bit truncation) with Number.parseInt(len, 10)
• Handles arbitrarily large Content-Length values up to Number.MAX_SAFE_INTEGER
• Preserves existing behavior for values under 2GB, including zero
• Add comprehensive test cases for overflow boundaries and edge cases

Fixes integer overflow where ~~'2147483648' returned -2147483648 instead of the correct value. Now correctly parses large file uploads and returns undefined for unparseable values, consistent with existing patterns.

Test Coverage

Added 6 comprehensive test cases covering:

• Zero value (edge case)
• Content-Length > 2GB (2147483648, 10000000000) — new capability
• Floating-point strings ('10.5') — truncation behavior preserved
• Non-numeric strings ('invalid') — returns undefined
• Empty string — already guarded by if check

All existing tests pass (439/439). No breaking changes.

Checklist

• I have ensured my pull request is not behind the main or master branch of the original repository.
• I have rebased all commits where necessary so that reviewing this pull request can be done without having to merge it first.
• I have written a commit message that passes commitlint linting.
• I have ensured that my code changes pass linting tests.
• I have ensured that my code changes pass unit tests.
• I have described my pull request and the reasons for code changes along with context if necessary.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 99.90%. Comparing base (e0ba8ef) to head (6903bc8).

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #1961   +/-   ##
=======================================
  Coverage   99.90%   99.90%           
=======================================
  Files           9        9           
  Lines        2105     2106    +1     
=======================================
+ Hits         2103     2104    +1     
  Misses          2        2           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[tejgokani]

@olleolleolle
Please take a look at this PR

[olleolleolle]

As a non-maintainer, and having read this patch only, I think it looks good. I recommend its merging.

[tejgokani]

Thank you so much for the approval. Could please tell me who approves for the merge, so that I may address the issue to them specifically.

[fengmk2]

@tejgokani Thanks!

[tejgokani]

Thank you so much to all the maintainers and contributors for the opportunity.

Regards,
tejgokani