[robjtede]

Accept case-insensitive byte range units in HttpRange::parse and parse_bytes, as required by RFC 9110 §14.1.

Use an ASCII case-insensitive prefix comparison without allocation, and add mixed-case inputs to the existing parser tests.

Fixes #12.

[bancek]

I did some benchmarking a custom unrolled check is faster:

fn has_bytes_unit(header: &[u8]) -> bool {
    if header.len() < PREFIX_LEN {
        return false;
    }

    let unit = &header[..PREFIX_LEN];
    ((unit[0] | 0x20) == b'b')
        & ((unit[1] | 0x20) == b'y')
        & ((unit[2] | 0x20) == b't')
        & ((unit[3] | 0x20) == b'e')
        & ((unit[4] | 0x20) == b's')
        & (unit[5] == b'=')
}

Implementation	Prefix check
starts_with (old behavior, lowercase input)	2.34 ns
eq_ignore_ascii_case (get/slice/first_chunk, all equal)	5.38 ns
manual | 0x20, branchless	2.37 ns
manual | 0x20, short-circuit &&	2.94 ns
masked u32 + u16	2.35 ns
to_ascii_lowercase allocation	18.93 ns

[bancek]

I released v0.1.6

https://crates.io/crates/http-range/0.1.6