Currently playing on dir.xiph.org (YP) URL-escaped about icecast-kh HOT 11 CLOSED

@karlheyes We can pull specific commits in our build process, no need to tag a release. I'll update our Rolling Release and let you know how things look. Thanks for your help!

from icecast-kh.

ok, lets get to this one. I'm assuming that if you are getting this here then the source is sending a doubly encoded metadata. Obviously I have to encode for sending to the YP and the source client has to encoded for sending in the GET, but if the source is reading from something that is already encoded then it will be doubly encoded in such cases.

I might be able to do a verification check to skip a step if it is ok to do so.

karl.

from icecast-kh.

I do not know what would be required for that. pulling the master tree vs a [pre-]release is not that much different but how that wraps up in a binary distribution is a different issue. I can cut a pre-release if that helps.

karl

from icecast-kh.

@Moonbase59 Latest Rolling Release has the latest commit from icecast-kh master. Try it out!

from icecast-kh.

Same issue here

from icecast-kh.

can you verify the master tree works as expected. looks to be a bug from the params work clashing with the older code.

karl

from icecast-kh.

Thanks for investigating. I fear we might need @BusterNeece for that, or a version I could easily install (not build) within the AzuraCast docker container… Would that be possible?

from icecast-kh.

@karlheyes @BusterNeece Thanks for your help!

Confirmed working with Icecast 2.4.0-kh21.3, build 2-g5f5564d. (At least with dir.xiph.org, I’ll try some others later.)

from icecast-kh.

Confirmed working with internet-radio.com, too.

Directory config used:

<directory>
    <yp-url-timeout>15</yp-url-timeout>
    <yp-url>http://dir.xiph.org/cgi-bin/yp-cgi</yp-url>
</directory>
<directory>
    <yp-url-timeout>15</yp-url-timeout>
    <yp-url>http://icecast-yp.internet-radio.com</yp-url>
</directory>

from icecast-kh.

@karlheyes Should we close this for now? (Since you were thinking of maybe changing the code later.)

from icecast-kh.

well that's fixed, and committed to master, will be rolled into next update. The change I was thinking of is just a question of when the encoding was done, a bunch of it was pruned out but not all. So not currently on the agenda. I'll close for now and thanks to everyone for flushing out the issue.

karl.

from icecast-kh.