[FFmpeg-trac] #6066(avformat:reopened): Handling HTTP 500 errors for input files

[FFmpeg]

#6066: Handling HTTP 500 errors for input files
-------------------------------------+------------------------------------
             Reporter:  dprestegard  |                    Owner:
                 Type:  enhancement  |                   Status:  reopened
             Priority:  wish         |                Component:  avformat
              Version:  unspecified  |               Resolution:
             Keywords:  http         |               Blocked By:
             Blocking:               |  Reproduced by developer:  0
Analyzed by developer:  0            |
-------------------------------------+------------------------------------

Comment (by brewerja):

 We too have struggled with using ffmpeg against files in S3. In our case,
 we are clipping and transcoding HLS streams that are fed into ffmpeg as an
 input.txt file listing tracks. When we do this for long clips where the
 input file contains >3K .ts files, we very often see the 500 Internal
 Server error error message from ffmpeg.

 The assumption has been that we are getting 500 errors sporadically from
 S3, but having tested a sequential curl of the same input file and even
 doing that in parallel, we are unable to reproduce a 500 error from S3.

 We can reproduce the error in a test if we use a mock web server and setup
 the server to throw a single 500 error. We've not had any luck with the
 reconnect flags.

 I feel our options are either try to implement some sort of retry outside
 of ffmpeg (via proxy) or download the .ts files locally before running
 ffmpeg.

--
Ticket URL: <https://trac.ffmpeg.org/ticket/6066#comment:10>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker