WebKit ought to be able to play videos without Content-Length HTTP header fields and without range support
Created attachment 442199 [details]
Comment on attachment 442199 [details]
View in context: https://bugs.webkit.org/attachment.cgi?id=442199&action=review
> + AVFoundation doesn't like it when you give it a range like 0-1/* because it doesn't know the content length.
> + To work around this, wait until the entire video is loaded then respond with a known length.
> + This isn't great, but it's better than not playing the video at all.
So, was the old behavior a race condition based on how fast the video loaded? How did this every work at all?
Created attachment 442376 [details]
It never did work.
Committed r284816 (243508@main): <https://commits.webkit.org/243508@main>
All reviewed patches have been landed. Closing bug and clearing flags on attachment 442376 [details].