From dd96c11d5e0166ce6c597d178ee4827193cff16d Mon Sep 17 00:00:00 2001 From: wm4 Date: Thu, 24 Jan 2013 16:05:52 +0100 Subject: stream: implement some HTTP specific options for stream_lavf The "http:" protocol has been switched to use ffmpeg's HTTP implementation some time ago. One problem with this was that many HTTP specific options stopped working, because they were obviously implemented for the internal HTTP implementation only. Add the missing things. Note that many options will work for ffmpeg only, as Libav's HTTP implementation is missing these. They will silently be ignored on Libav. Some options we can't fix: --ipv4-only-proxy, --prefer-ipv4, --prefer-ipv6 As far as I can see, not even libavformat internals distinguish between ipv4 and ipv6. --user, --passwd ffmpeg probably supports specifying these in the URL directly. --- stream/cookies.c | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) (limited to 'stream/cookies.c') diff --git a/stream/cookies.c b/stream/cookies.c index d8f8b051f9..5d772b8a6a 100644 --- a/stream/cookies.c +++ b/stream/cookies.c @@ -261,3 +261,24 @@ cookies_set(HTTP_header_t * http_hdr, const char *domain, const char *url) http_set_field(http_hdr, buf); free(buf); } + +// Return a cookies string as expected by lavf (libavformat/http.c). The format +// is like a Set-Cookie header (http://curl.haxx.se/rfc/cookie_spec.html), +// separated by newlines. +char *cookies_lavf(void) +{ + if (!cookie_list) + cookie_list = load_cookies(); + + struct cookie_list_type *list = cookie_list; + char *res = talloc_strdup(NULL, ""); + + while (list) { + res = talloc_asprintf_append_buffer(res, + "%s=%s; path=%s; domain=%s; %s\n", list->name, list->value, + list->path, list->domain, list->secure ? "secure" : ""); + list = list->next; + } + + return res; +} -- cgit v1.2.3