#6066: Handling HTTP 500 errors for input files
-------------------------------------+------------------------------------
Reporter: dprestegard | Owner:
Type: enhancement | Status: closed
Priority: normal | Component: avformat
Version: unspecified | Resolution: invalid
Keywords: http | Blocked By:
Blocking: | Reproduced by developer: 0
Analyzed by developer: 0 |
-------------------------------------+------------------------------------
Comment (by dprestegard):
Why was this closed? I verified that using reconnect_at_eof does not
resolve the issue.
The 500 error handling could still be drastically improved with some retry
logic. With storage systems increasingly moving toward object storage and
more workloads moving to cloud services this type of issue will only
happen more often in the future.
Is there anything else I can provide? I'll work on generating a source
file and procedure for reproducing the issue.
--
Ticket URL: <https://trac.ffmpeg.org/ticket/6066#comment:5>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
_______________________________________________
FFmpeg-trac mailing list
[email protected]
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac
