invalid start and end byte ranges should return -2

[mreinstein]

Expected:

parse(200, 'bytes=x-100') === -2

Actual:

parse(200, 'bytes=x-100') === [ { start: 0, end: 199 }, type: 'bytes' ]

[JakeChampion]

@mreinstein is this bug fixed for you?

[dougwilson]

Hmm, i don't think it's fixed. The PR with the fix looks like it was closed too. Looks like the original pr came in while I was dealing with a hurricane and then there was a ping while I was on a work trip that I forgot to respond to. Not sure why they ended up closed now. I'll reopen this @JakeChampion and I think I can pluck the changes from that PR to master still.

[mreinstein]

@mreinstein is this bug fixed for you?

Not fixed. I was trying to get the PR through but didn't seem like there was any momentum or follow through. 10 months later, nothing has changed.

[wesleytodd]

Hey @mreinstein, sorry this is a group of unpaid volunteers, please have patience. Would you be willing to re-open a PR for this?