I am using your solution to serve a video on my website and I found out an interesting bug.
If you serve a webm video encoded with the vp9 codec (not supported by Safari), there is a glitch in Safari and the browser will request many chunks of the video. It will consequently use multiple connections and quickly reach the maximum number of connections if you are behind Apache. After a few seconds, you server won't be responding to any request. I had to close the page to stop the loop and reload Apache to put back my server on feet.
But I do not know why I cannot reproduce the bug in local, it occurs only on my production server...
Of course I changed the video for one with the vp8 codec but I wanted to share my experience because I struggled to understand why my server was breaking down today for no reason.
I am using your solution to serve a video on my website and I found out an interesting bug.
If you serve a webm video encoded with the vp9 codec (not supported by Safari), there is a glitch in Safari and the browser will request many chunks of the video. It will consequently use multiple connections and quickly reach the maximum number of connections if you are behind Apache. After a few seconds, you server won't be responding to any request. I had to close the page to stop the loop and reload Apache to put back my server on feet.
But I do not know why I cannot reproduce the bug in local, it occurs only on my production server...
Of course I changed the video for one with the vp8 codec but I wanted to share my experience because I struggled to understand why my server was breaking down today for no reason.