[FFmpeg-trac] #7133(undetermined:reopened): [FFProbe] invalid byte range requests

FFmpeg trac at avcodec.org
Mon Aug 5 12:12:08 EEST 2019

#7133: [FFProbe] invalid byte range requests
             Reporter:  tjenkinson   |                    Owner:
                 Type:  defect       |                   Status:  reopened
             Priority:  normal       |                Component:
                                     |  undetermined
              Version:  git-master   |               Resolution:
             Keywords:               |               Blocked By:
             Blocking:               |  Reproduced by developer:  0
Analyzed by developer:  0            |
Changes (by bubbleguuum):

 * status:  closed => reopened
 * resolution:  needs_more_info =>


 I have observed the same thing on *some* (but not all) mp4 http streams
 hosted on Google Drive.
 ffproble will hammer the server like mad with repeated bogus Range
 requests resulting in 416 until eventually stopping after a minute or two.
 This would not be so bad if it didn't trigger Google Drive max download
 request limit for the file and flagging it *permanently* as not
 downloadable due to reaching max quota allowed (all subsequent access
 result in a 403).
 ffprobe should not be doing these random Range requests, this is bogus and
 unnecessary and has a nasty side effect on Google Drive and other quota
 limiting servers due to the extreme hammering.

Ticket URL: <https://trac.ffmpeg.org/ticket/7133#comment:2>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker

More information about the FFmpeg-trac mailing list