为提升您的使用体验,本站正在维护,部分功能暂时无法使用。如果本站文章无法解决您的问题,您想要向社区提问的话,请到 Twitter 上的 @FirefoxSupport 或 Reddit 上的 /r/firefox 提问,我们的支持社区将会很快回复您的疑问。

搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

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

  • 1 个回答
  • 2 人有此问题
  • 1 次查看
  • 最后回复者为 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.

所有回复 (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