I suggest you ...

XSL for icecast


In addition for the icecast crossdomain.xml file you have to create to get it work you could maybe better use the XSL way and generate a file.

This prevents you having to create the mimetype file.

For example I have icecast running in a Jail on FreeBSD which means I can't access any other files than the files in the icecast directroy.

In the icecast config you point crossdomain.xml to the XSL file and you are ready to go.

If you want to have the details on this, please let me know I'll hook you guys up with a tutorial.

13 votes
Sign in
Sign in with: facebook google
Signed in as (Sign out)
You have left! (?) (thinking…)
Marius van Witzenburg shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →


Sign in
Sign in with: facebook google
Signed in as (Sign out)
  • Walter commented  ·   ·  Flag as inappropriate

    Icecast v2.4.1 allows for CORS by adding the following to your Icecast config file.

    <http-headers><header name="Access-Control-Allow-Origin" value="*" /></http-headers>

    I'm having a hard time understanding what player and config I need to enable metadata on Muses player. All the chats seem to be back in 2012 where developers promise instructions and new info about it coming soon.

  • AdminFederico Bricker (CEO, Muses Radio Player) commented  ·   ·  Flag as inappropriate

    Hi, we're working now on the HTML5 version of Muses (as now is the default version).
    So I guess less people will need a tutorial for the crossdomain.xml and XSL, but it'll still be useful for some cases.

    If you have this, please let us know so we can make it available for more people.

    Also, if you have details on how to enable the javascript cross-origin policies on icecast / shoutcast, it'll be very useful :)


Feedback and Knowledge Base