Icecast - Nov 2018 - Custom Hooks

I am looking for a way that I can use to send a hook to my api when
particular things happen.

For instance, i need to know when listeners or sources connect or
disconnect and when song meta data changes on a stream.

I see this data on the log and can write a script to do it by monitoring
the log but does icecast have a better way?

Almost looks like the auth block could do it but I don't want to prompt
listeners for a login.

Thanks
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.xiph.org/pipermail/icecast/attachments/20181102/89bb98b5/attachment.html>

On 11/02/2018 11:41 PM, Alex Hackney wrote:
> I am looking for a way that I can use to send a hook to my api when
> particular things happen.
>
> For instance, i need to know when listeners or sources connect or
> disconnect and when song meta data changes on a stream.
>
> I see this data on the log and can write a script to do it by
> monitoring the log but does icecast have a better way?
>
> Almost looks like the auth block could do it but I don't want to
> prompt listeners for a login.
>
That's actually how you do it. You use the URL-auth backend and always
return positive authentication.

Please make sure that you are running version 2.4.4 though. Older
versions have a security issue in the URL-auth code!

Cheers,

TBR

When I stream with winamp, it appears to ask for a username and password
Everytime. If I just set the return to true no matter what, will it prevent
the client from asking for a password?

On Sun, Nov 4, 2018, 06:57 Thomas B. Rücker <thomas at ruecker.fi wrote:
>
>
> On 11/02/2018 11:41 PM, Alex Hackney wrote:
> > I am looking for a way that I can use to send a hook to my api when
> > particular things happen.
> >
> > For instance, i need to know when listeners or sources connect or
> > disconnect and when song meta data changes on a stream.
> >
> > I see this data on the log and can write a script to do it by
> > monitoring the log but does icecast have a better way?
> >
> > Almost looks like the auth block could do it but I don't want to
> > prompt listeners for a login.
> >
>
> That's actually how you do it. You use the URL-auth backend and always
> return positive authentication.
>
> Please make sure that you are running version 2.4.4 though. Older
> versions have a security issue in the URL-auth code!
>
> Cheers,
>
> TBR
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.xiph.org/pipermail/icecast/attachments/20181107/1080455f/attachment.html>