[FFmpeg-trac] #9700(ffprobe:new): "451 Unavailable For Legal Reasons" instead of just HTTP_OTHER_4XX error
FFmpeg
trac at avcodec.org
Thu Apr 21 15:53:45 EEST 2022
#9700: "451 Unavailable For Legal Reasons" instead of just HTTP_OTHER_4XX error
---------------------------------------+-----------------------------------
Reporter: Owyn | Owner: (none)
Type: defect | Status: new
Priority: normal | Component: ffprobe
Version: unspecified | Resolution:
Keywords: 451 error 4XX | Blocked By:
Blocking: | Reproduced by developer: 0
Analyzed by developer: 0 |
---------------------------------------+-----------------------------------
Comment (by Stefano Sabatini):
So, if you are using it in a script I guess you are parsing the error
code:
{{{
$ ./ffprobe https://strm.yandex.ru/kal/rbc/rbc0.m3u8 -show_format
-show_error
ffprobe version N-106634-gbb6ef6d314 Copyright (c) 2007-2022 the FFmpeg
developers
built with gcc 9 (Ubuntu 9.4.0-1ubuntu1~20.04.1)
configuration: --enable-openssl
libavutil 57. 24.101 / 57. 24.101
libavcodec 59. 26.100 / 59. 26.100
libavformat 59. 22.100 / 59. 22.100
libavdevice 59. 6.100 / 59. 6.100
libavfilter 8. 33.100 / 8. 33.100
libswscale 6. 6.100 / 6. 6.100
libswresample 4. 6.100 / 4. 6.100
[https @ 0x5573b693f640] HTTP error 451 Unavailable For Legal Reasons
https://strm.yandex.ru/kal/rbc/rbc0.m3u8: Server returned 4XX Client
Error, but not one of 40{0,1,3,4}
[ERROR]
code=-1482175736
string=Server returned 4XX Client Error, but not one of 40{0,1,3,4}
[/ERROR]
}}}
But then the only solution would be to add a specific error code for the
451 error.
Do you confirm?
--
Ticket URL: <https://trac.ffmpeg.org/ticket/9700#comment:3>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
More information about the FFmpeg-trac
mailing list