send 416 error to overlapping ranges request

[Chenjp]

request ranges validation - overlap detection added.

• invalid ranges - overlapping:

D:\git\github.com>curl http://localhost:55464/index.html -i -H "Range: bytes=10-40,35-50"
HTTP/1.1 416
Accept-Ranges: bytes
Content-Range: bytes */957
Content-Type: text/html;charset=utf-8
Content-Language: zh-CN
Content-Length: 753
Date: Tue, 19 Nov 2024 03:03:56 GMT

• valid ranges:

D:\git\github.com>curl http://localhost:55464/index.html -i -H "Range: bytes=10-40,50-60"
HTTP/1.1 206
Accept-Ranges: bytes
ETag: W/"957-1724403887512"
Last-Modified: Fri, 23 Aug 2024 09:04:47 GMT
Content-Type: multipart/byteranges; boundary=CATALINA_MIME_BOUNDARY
Content-Length: 194
Date: Tue, 19 Nov 2024 03:04:39 GMT


--CATALINA_MIME_BOUNDARY
Content-Range: bytes 10-40/957

censed to the Apache Software F
--CATALINA_MIME_BOUNDARY
Content-Range: bytes 50-60/957

 (ASF) unde
--CATALINA_MIME_BOUNDARY--

[gmshake]

Nice catch!

[markt-asf]

I'd like to see similar protection for Content-Range when used with partial PUT.

[markt-asf]

I like this optimisation

[Chenjp]

I'd like to see similar protection for Content-Range when used with partial PUT.

@markt-asf done with PR #778
Only one content-range ( bytes {start}-{end}/{length} ) is allowed in partial PUT.

[markt-asf]

Tx. Applied a variation manually.