[FFmpeg-trac] #7695(undetermined:new): ffmpeg is ignoring -headers option

[FFmpeg]

#7695: ffmpeg is ignoring -headers option
-------------------------------------+-------------------------------------
             Reporter:  Anan5a       |                    Owner:
                 Type:  defect       |                   Status:  new
             Priority:  normal       |                Component:
              Version:  git-master   |  undetermined
             Keywords:               |               Resolution:
             Blocking:               |               Blocked By:
Analyzed by developer:  0            |  Reproduced by developer:  0
-------------------------------------+-------------------------------------

Comment (by barsnick):

 I agree that the command line is bogus, for several reasons:

 * The URL given in the referer is misspelled, and therefore probably
 useless, because if the server really requires it, it will not validate
 correctly.
 * The content the reporter is likely trying to download ("Sultan: The
 Saviour") is probably protected by (at least) a login. I may be wrong, and
 it's only the video's web page which is login-protected.
 * Assuming that the m3u8 file references http(s) hls segments, recent
 ffmpeg's command line requires a "`-protocol_whitelist`" to allow loading
 them.

 On the other hand, the report is correct in so far that it does not seem
 possible to give ffmpeg command line options meant for e.g. protocols
 triggered "underneath". I.e. ffmpeg launches with a file protocol input
 which promotes to hls, but this in turn may trigger http protocol
 segments, yet ffmpeg will refuse to accept http protocol options on the
 command line.

 Some ''muxers'' have ways of achieving this: The `tee` muxer has a special
 syntax, the `segment` muxer has "`-segment_format_options`", the `dash`
 muxer has "`-format_options`", the fifo muxer has "`-format_opts`". I
 don't see this for the `hls` demuxer (which is used in this example)
 though. The `hls` demuxer ''does'' expose some http protocol options via
 its own proxy options ("`-http_persistent`", "`-http_multiple`"), but
 "`-headers`" does not belong to those.

 So, this may actually be a feature request...

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