Origin Server accepts m3u8 where segment entries contain the #EXT-X-BYTERANGEtag. For such segment entries, the actual HTTP GET request for segments contains the Range headers. Origin Server doesn't honor such requests for syntactically valid Range headers. It sends a response with a status of 206 (Partial Content) containing the applicable ranges of the entity-body. For such response, the Content-Range entity-header is sent and it specifies where in the full entity-body and the partial body should be applied.
If the byte-range-set is cannot be fulfilled, the server returns a response with a status of 416 (Requested range not satisfiable).
Origin Server supports only single byte range in the byte range set (including support for suffix byte range.) If more than one byte range is specified in the byte range set, Origin Server ignores the byte-range-set and serves the entire entity.