Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Too many duplicate requests to the server, playing HTML5 video.

  • 1 reply
  • 2 have this problem
  • 3 views
  • Last reply by guigs

more options

Hi guys. In Firefox, when I open a tab that has a HTML5 video in it, if it is "preload='auto'" or "autoplay", it sends too many repetitious requests to the server. The server responds 206 according to the ranges requested, but FF again sends the same request to the server. they happen on page load. (I mean too many repetitious requests, until sever I/O hangs!) But if it is "preload='none'", same headers are sent after playing the video.

    • And beyond this problem, the main problem is that Firefox doesn't play the video until it downloads it completely.

These 2 problems occur when I play video using FF's native operation or by using a jquery plugin like video.js. in Chrome and Opera there is no problem. I have attached 2 photos to show you the problems by detailed. I am using Firefox 40.

Thanks.

Hi guys. In Firefox, when I open a tab that has a HTML5 video in it, if it is "preload='auto'" or "autoplay", it sends too many repetitious requests to the server. The server responds 206 according to the ranges requested, but FF again sends the same request to the server. they happen on page load. (I mean too many repetitious requests, until sever I/O hangs!) But if it is "preload='none'", same headers are sent after playing the video. ** And beyond this problem, the main problem is that Firefox doesn't play the video until it downloads it completely. These 2 problems occur when I play video using FF's native operation or by using a jquery plugin like video.js. in Chrome and Opera there is no problem. I have attached 2 photos to show you the problems by detailed. I am using Firefox 40. Thanks.

All Replies (1)

more options

AFAIK the preload=auto will not play the video until the page has loaded all the way. These requests for ranged would success in 206 status. The work arounds mentioned on the internet are to set "preload='none'", but you are seeing that it sends the same headers.

Other bugs mentioning this:

References

I apologize it looks like the trail ends there, I would be happy to help pick this back up I will ask in #media