[FFmpeg-trac] #2180(avformat:new): http: cookie bugs

[FFmpeg]

#2180: http: cookie bugs
------------------------------------+------------------------------------
             Reporter:  gjdfgh      |                    Owner:
                 Type:  defect      |                   Status:  new
             Priority:  normal      |                Component:  avformat
              Version:  git-master  |               Resolution:
             Keywords:              |               Blocked By:
             Blocking:              |  Reproduced by developer:  0
Analyzed by developer:  0           |
------------------------------------+------------------------------------

Comment (by gjdfgh):

 {{{
 $ ffmpeg -cookies "NAME=VALUE; path=/; domain=localhost; secure " -i
 http://localhost:10000/test.mkv
 ffmpeg version N-49529-gb45a3e1 Copyright (c) 2000-2013 the FFmpeg
 developers
   built on Feb  2 2013 13:06:37 with gcc 4.7 (Debian 4.7.2-5)
   configuration: --prefix=/tmp/fftemp
   libavutil      52. 17.100 / 52. 17.100
   libavcodec     54. 91.100 / 54. 91.100
   libavformat    54. 61.104 / 54. 61.104
   libavdevice    54.  3.103 / 54.  3.103
   libavfilter     3. 35.100 /  3. 35.100
   libswscale      2.  2.100 /  2.  2.100
   libswresample   0. 17.102 /  0. 17.102
 }}}

 Receiving side:

 {{{
 $ nc -l -p 10000
 GET /test.mkv HTTP/1.1
 User-Agent: Lavf54.61.104
 Accept: */*
 Range: bytes=0-
 Connection: close
 Host: localhost:10000
 Cookie: (null)

 }}}

 "(null)" is obviously not a valid cookie value. This demonstrates the two
 issues I pointed out.

 Also, I've noticed an unrelated cookie issue: with some sites, ffmpeg
 seems to accumulate "bad cookies". You can try with [https://github.com
 /mpv-player/mpv mpv] and vimeo links. On every seek (http reconnect),
 ffmpeg prints an additional warning reading "[http @ 0x8a43da0]Invalid
 cookie found, no value, path or domain specified" (e.g. the 10th seek will
 print 10 such messages). However, I'm far too lazy to analyze this.

-- 
Ticket URL: <https://ffmpeg.org/trac/ffmpeg/ticket/2180#comment:4>
FFmpeg <http://ffmpeg.org>
FFmpeg issue tracker