Ranges should be inclusive or not. But not both.

Starting in 0 and ending in 1024 doesn't gets the byte 1024

It should include the ending byte or it should be called "before" instead "end"

WIth the current status if I want only the byte 18635 I need to ask for 18635-18636.
I think if the 1st byte is included the last should be included too. Having a range that is inclusive in the beginning and exclusive in the end is very counterintuitive.

The issue does not name a file or test; start by locating range parsing and byte-boundary handling in the C nginx module. Confirm the intended inclusive or exclusive convention, then verify behavior for a range ending at 1024 and for requesting a single byte.

Written by the indexing model from the issue text.