Describe the bug
The range header provided by Api endpoint is non inclusive this prevents concurrent downloaders which uses range headers to produce corrupt parts
expected: Range: bytes=0-499 should give 500 bytes
actual: Range: bytes=0-499 gives 499 bytes
the first curl gives a corrupt file, where as the 2nd one gives the correct file, this is not the desired behavior as http range headers should be inclusive first curl should produce the correct file.
Describe the bug The range header provided by Api endpoint is non inclusive this prevents concurrent downloaders which uses range headers to produce corrupt parts
expected:
Range: bytes=0-499
should give 500 bytes actual:Range: bytes=0-499
gives 499 byteshttps://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Range
Reproduce
trying to download OpenTTD with a size of 7304357 bytes from demo server.
the first curl gives a corrupt file, where as the 2nd one gives the correct file, this is not the desired behavior as http range headers should be inclusive first curl should produce the correct file.