Hej,
On Thu, 20 Aug 2020, Moritz Barsnick wrote:
Hej Martin,
On Thu, Aug 20, 2020 at 22:05:39 +0300, Martin Storsjö wrote:
Even if you do e.g. a plain tls socket (or rtmps, or whatever), you may
want to do the tls connection through a proxy server (be that a socks
proxy or http proxy).
Actually, I forget that an HTTP proxy with CONNECT support cn transport
any plain socket. I will amend documentation to doc/*.texi.
For the case of rtmps, if you pass the http_proxy option, it should be
passed to the rtmps protocol, which doesn't have such an option, from
where it's passed along in the options dictionary down until the tls
protocol consumes it.
So you're saying it already works for rtmps, nothing needs to be
changed there? Fine.
I didn't test it, but from browsing the code, it looks like it would work.
// Martin
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
