[question / request] Set ffmpegdirect proxy via #KODIPROP in strm / m3u files

[enerdude]

As my title indicates, is it possible to set this on a per stream basis otherwise one needs to change the setting everytime in addon settings.

I also to refer to an old discussion:
https://forum.kodi.tv/showthread.php?tid=248440

[phunkyfish]

It should be possible to set this as a KODIPROP, although that use case is not currently supported. Let me take a look.

Can you test something on Kodi 22 if I figure out how to do it?

[phunkyfish]

#310

Will let you know once testbuilds are available, it can take a while to build.

[phunkyfish]

Testbuilds: https://jenkins.kodi.tv/blue/organizations/jenkins/xbmc%2Finputstream.ffmpegdirect/detail/PR-310/1/artifacts

[enerdude]

Testbuilds: https://jenkins.kodi.tv/blue/organizations/jenkins/xbmc%2Finputstream.ffmpegdirect/detail/PR-310/1/artifacts

Thanks, will test and let you know

[enerdude]

Ok seems to work fine. What I tried:

#EXTINF:-1,Example HLS stream
#KODIPROP:inputstream=inputstream.ffmpegdirect
#KODIPROP:mimetype=application/vnd.apple.mpegurl
#KODIPROP:inputstream.ffmpegdirect.manifest_type=hls
#KODIPROP:inputstream.ffmpegdirect.http_proxy_host=127.0.0.1
#KODIPROP:inputstream.ffmpegdirect.http_proxy_port=8081
https://example.com/index.m3u8
using
latest Kodi 22 nightly build using the above ffmpegdirect you compiled.

I have a question:

For Kodi to pass the proxy parameters to ffmpegdirect via the '|' pipe, I assume a new compile of Kodi is needed?
e.g.
#EXTINF:-1,Example HLS stream
https://example.com/index.m3u8|httpproxy=http://username:password@127.0.0.1:8081

This will also mean that e.g. inputstream.adaptive will also be compatible with a proxy when used in this way?

At the moment "httpproxy=http://username:password@127.0.0.1:8081" is sent as header value, e.g.
httpproxy: http://username:password@127.0.0.1:8081

[phunkyfish]

Nope, it should work wth the | already. The ffmpeg property is called http_proxy and not httproxy.

This is only for ffmpegdirect. I'm not sure what adaptive supports.

[enerdude]

Nope, it should work wth the | already.

No it does not, tried it again. It adds a header to the request like this:
http_proxy: http://127.0.0.1:8081
where 127.0.0.1:8081 is the proxy I specified

It is also clear from the abovementioned kodi forum thread that it is an issue since 2015 already and could be a security risk as proxy details is sent via headers to remote server.

Where should I open an issue for this?

[phunkyfish]

So it doesn’t use the proxy at all and just adds a header instead?

what’s wrong with using the kodiprops?

[phunkyfish]

I think I see where the value get's treateed the wrong way. Let me update the PR and give you some new testbuilds.

[phunkyfish]

Ok, can you try these testbuilds and see if it works via a |?

https://jenkins.kodi.tv/blue/organizations/jenkins/xbmc%2Finputstream.ffmpegdirect/detail/PR-310/3/artifacts

[enerdude]

Ok, can you try these testbuilds and see if it works via a |?

https://jenkins.kodi.tv/blue/organizations/jenkins/xbmc%2Finputstream.ffmpegdirect/detail/PR-310/3/artifacts

Ok should I test like this?

http://www.somewhere.com/playlist.m3u8|http_proxy=http://127.0.0.1:8080

[enerdude]

So it doesn’t use the proxy at all and just adds a header instead?

what’s wrong with using the kodiprops?

I guess nothing. I was also wondering...what is default behaviour if I put an entry in m3u playlist and don't specify input.ffmpegdirect in the #KODIPROP, will it use inputstream.adaptive by default? (I think this is my experience so far)

Also, I will have to open a issue for adaptive to also add proxy support?

[enerdude]

Ok should I test like this?

http://www.somewhere.com/playlist.m3u8|http_proxy=http://127.0.0.1:8080

I tested this way as well as changing it to httpproxy but both are still added as headers. Like I said I can use the KODIPROPS way, I just thought it would be a more uniform way to do via the "|", then adaptive can also get sent the proxy info without the need for seperate #KODIPROP

[phunkyfish]

Ffmpeg supports a http proxy. Adaptive issues a different library so I don’t know if it can support a proxy at all.

[phunkyfish]

Can you try one more test build:

https://jenkins.kodi.tv/blue/organizations/jenkins/xbmc%2Finputstream.ffmpegdirect/detail/PR-310/6/artifacts

This one simply add a log line to see if http_proxy is correctly set from a | symbol. When you test it see if there is a log line starting with XXX.