[FFmpeg-trac] #11058(avformat:new): Optimize HTTP request header to workaround simple access blocks

FFmpeg trac at avcodec.org
Sun Jun 23 16:24:40 EEST 2024


#11058: Optimize HTTP request header to workaround simple access blocks
-------------------------------------+-------------------------------------
             Reporter:               |                    Owner:  (none)
  randomcoder67                      |
                 Type:  enhancement  |                   Status:  new
             Priority:  normal       |                Component:  avformat
              Version:  git-master   |               Resolution:
             Keywords:  http         |               Blocked By:
             Blocking:               |  Reproduced by developer:  0
Analyzed by developer:  0            |
-------------------------------------+-------------------------------------
Comment (by randomcoder67):

 Replying to [comment:2 MasterQuestionable]:
 > ͏    Unrecoverable network problem:
 > ͏    HTTP 404 is the typical message. (obscure access denial, or really
 just "Not Found")
 >
 > ͏    See also:
 > ͏    https://trac.ffmpeg.org/ticket/11024#comment:2
 >
 > ͏    Try experimenting the relevant HTTP request headers?
 > ͏    If VLC alike could somehow seemingly properly work.
 >
 > ͏    Excerpt from "log.txt":
 > [[
 > ͏    User-Agent: Lavf/60.16.100
 > ͏    Accept: */*
 > ͏    Connection: close
 > ͏    Host: vs-cmaf-pushb-uk-live.akamaized.net
 > ͏    Icy-!MetaData: 1
 > ]]
 > ͏    See also:
 > ͏    https://browserleaks.com/ip#headers
 > ͏    https://github.com/MasterInQuestion/talk/discussions/10
 >
 > ͏    Make your access pattern more like the expected initiator should
 workaround.
 > ͏    Note there are channels other than request headers.

 I tried using the same headers as VLC:

 {{{ffmpeg -headers $'Host: vs-cmaf-pushb-uk-
 live.akamaized.net:443\r\nAccept: */*\r\nAccept-Language: en_GB\r\nUser-
 Agent: VLC/3.0.21 LibVLC/3.0.21\r\nAccept-Encooding: deflate, gzip\r
 \nCache-Control: no-cache\r\n' -i "$URL" -y  out.mp4}}}

 The same issue happens. The headers do seem to be used as they can be seen
 in the output of ffmpeg with {{{-v debug}}}

 You mentioned there are channels other than request headers. What would
 those be?
-- 
Ticket URL: <https://trac.ffmpeg.org/ticket/11058#comment:4>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker


More information about the FFmpeg-trac mailing list