Thank you Ted! I totally overlooked the text and thought "path" and "domains" are just the cookie content in that example.
On Wed, Sep 23, 2020 at 11:19 PM Benjamin Peng <human.p...@gmail.com> wrote: > I'm trying to set cookies for a HLS request. > > >ffmpeg -v 99 -cookies "test=blabla;" -i > https://del.thumva.com/hls/20200621-0005-05/index_1.m3u8 > > But the request doesn't actually include my cookie: > > [https @ 00000000005f7100] request: GET /hls/20200621-0005-05/index_1.m3u8 > HTTP/1.1 > User-Agent: Lavf/58.51.100 > Accept: */* > Range: bytes=0- > Connection: close > Host: del.thumva.com > Icy-MetaData: 1 > > If I use "headers" instead, it works fine: > > >ffmpeg -v 99 -headers "Cookie: test=blabla;" -i > https://del.thumva.com/hls/20200621-0005-05/index_1.m3u8 > > [https @ 0000000000446040] request: GET /hls/20200621-0005-05/index_1.m3u8 > HTTP/1.1 > User-Agent: Lavf/58.51.100 > Accept: */* > Range: bytes=0- > Connection: close > Host: del.thumva.com > Icy-MetaData: 1 > Cookie: test=blabla; > > Why is it like this? Did I understand the "cookies" option wrong? > _______________________________________________ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".