Kikobeats / get-content-length

97%

push

github

fix: do not treat a 206 partial Content-Length as the resource size (#28)

* fix: do not treat a 206 partial Content-Length as the resource size

A satisfied range with an unknown total (bytes 0-0/*) still carries
Content-Length for the selected byte. Using that as the resource size
made reachable-url / GitHub probes report length 1.

Co-authored-by: kikohumanbeatbox <kikohumanbeatbox@gmail.com>

* refactor: normalize headers inside the unknown-range check

Callers no longer wrap the same headers before asking whether a 206 total is unknown.

Co-authored-by: Cursor <cursoragent@cursor.com>

---------

Co-authored-by: Cursor Agent <cursoragent@cursor.com>
Co-authored-by: kikohumanbeatbox <kikohumanbeatbox@gmail.com>
Co-authored-by: Kiko Beats <josefrancisco.verdu@gmail.com>

33 of 36 branches covered (91.67%)

Branch coverage included in aggregate %.

21 of 21 new or added lines in 1 file covered. (100.0%)

83 of 84 relevant lines covered (98.81%)

4.46 hits per line