[FFmpeg-devel] [PATCH] Maintain HTTP options across multiple requests in HLS demuxer

Micah Galizia micahgalizia at gmail.com
Wed Jan 9 03:20:44 CET 2013

On Tue, Jan 8, 2013 at 8:07 AM, Michael Niedermayer <michaelni at gmx.at>wrote:

> On Sat, Jan 05, 2013 at 11:23:11AM -0500, Micah Galizia wrote:
> > Hello,
> >
> > After a discussion on IRC it was suggested that http add a cookies
> > option and hls broker the http options between different http
> > requests. Attached is a patch that does that.
> >
> > The cookies are stored as the string value of the "Set-Cookie: " field
> > delimited by a newline when more than one set cookie field was sent.
> > Then when making a request, they are parsed and added to the header.
> Do you have some testcase / how can this be tested ?

I'm not sure how one would go about integrating this into an automated
regression system (short of setting up my own server). I do my testing
either against the fox servers that require this, but I also have another
stream that actually echo's back cookies based on the URI. For example:

 ./ffplay -user-agent micah "

will response with a "Set-Cookie: nlqptid=ffmpeg=neato..." header field. In
either case I validate the requests with wireshark.

Is this sufficient proof?
"The mark of an immature man is that he wants to die nobly for a cause,
while the mark of the mature man is that he wants to live humbly for
one."   --W. Stekel

More information about the ffmpeg-devel mailing list