[FFmpeg-trac] #11394(undetermined:new): ffmpeg ignores -seekable 0 when requesting hls key

FFmpeg trac at avcodec.org
Thu Jan 2 18:05:43 EET 2025


#11394: ffmpeg ignores -seekable 0 when requesting hls key
-------------------------------------+-------------------------------------
             Reporter:  mmis1000     |                    Owner:  (none)
                 Type:  defect       |                   Status:  new
             Priority:  normal       |                Component:
                                     |  undetermined
              Version:  unspecified  |               Resolution:
             Keywords:  hls          |               Blocked By:
             Blocking:               |  Reproduced by developer:  0
Analyzed by developer:  0            |
-------------------------------------+-------------------------------------
Description changed by mmis1000:

Old description:

> Summary of the bug:
> How to reproduce:
> {{{
> % ffmpeg -v debug -seekable 0 -icy 0 -f hls -i 'https://path-to-
> hls.host/manifest' test.mp4
> ffmpeg version 4.4.2-0ubuntu0.22.04.1 Copyright (c) 2000-2021 the FFmpeg
> developers
>
> ...
>
> [https @ 0x5b494dcf0700] request: GET /manifest HTTP/1.1
> Accept: */*
> Connection: close
> Host: path-to-hls.host
> ...
>
> [https @ 0x5b494dcfbf00] request: GET /key HTTP/1.1
> Accept: */*
> Range: bytes=0-
> Connection: keep-alive
> Host: path-to-hls.host
> }}}
>
> The manifest itself does obey -seekable 0 and not sent with range header.
> But the key file always send with range header no matter you set it as
> seekable or not and also there is no other way to disable range header.

New description:

 Summary of the bug:
 How to reproduce:
 {{{
 % ffmpeg -v debug -seekable 0 -icy 0 -f hls -i 'https://path-to-
 hls.host/manifest' test.mp4
 ffmpeg version 4.4.2-0ubuntu0.22.04.1 Copyright (c) 2000-2021 the FFmpeg
 developers

 ...

 [https @ 0x5b494dcf0700] request: GET /manifest HTTP/1.1
 Accept: */*
 Connection: close
 Host: path-to-hls.host

 ...

 [https @ 0x5b494dcfbf00] request: GET /key HTTP/1.1
 Accept: */*
 Range: bytes=0-
 Connection: keep-alive
 Host: path-to-hls.host
 }}}

 The manifest itself does obey -seekable 0 and not sent with range header.
 But the key file always send with range header no matter you set it as
 seekable or not and also there is no other way to disable range header.

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


More information about the FFmpeg-trac mailing list