fixed
2024-10-17
2 months ago
Byte-range requests
We had an issue with HTTP requests that included one or more range HTTP headers (byte-range) on our manipulated manifests (that we were answering with an HTTP 206). This impacted insertions and ad replacements for the application Dynamic Ad Insertion.
We are happy to report that we fixed the problem, and you can now continue to use byte-range requests.
As a reminder, our platform returns HTTP response status code 206: Partial Content to indicate that an HTTP request has been completed and that the message body contains the requested data ranges.