Yeah, same deal. My hail mary guess is that it has something to do with Azure not returning `Accept
Yeah, same deal.
My hail mary guess is that it has something to do with Azure not returning
My hail mary guess is that it has something to do with Azure not returning
Accept-range: bytes header by default, even though it does support streaming, and Media Transformations relying on that header now

