This page is IMPORTANT and you should print it out or read it carefully. It contains information on a security update to Flash Player 9 that may prevent Minicaster pro-ICE from delivering track data.
Starting with Flash Player 9 Update 3 (9.0.115.0) Adobe have implemented a strict policy on the format and meta type for the 'crossdomain.xml' policy file. This file must be collected by Flash Player before any text files can be read from a remote server, and is critical to the collection of now-playing data by Minicaster pro-ICE. Details of the changes can be found here.
The crucial chage for Icecast users is that the server content type for the file MUST be 'text/*' or '*/xml'. The current builds of Icecast (2.3.1) have two ways to decide on the content-type for a file - firstly they try to locate the extension in the system mime.types file, then if they fail to locate it they default to using the content-type 'application/octet-stream'.
If your Icecast server is configured not to use 'chroot' setting, then it should be able to read the main Unix/Linux mime types file located at /etc/mime.types and all you need to do is make sure this file contains an entry for the XML file extension.
If your Icecast server is configured to use 'chroot' setting, then it will look for the Unix/Linux mime types file but assume it is located at [Icecast install dir]/etc/mime.types and you must either create a link from there to the genuine file, or place a copy there. If you do not, then Icecast will believe the mime.types file is missing and use the default octet-stream content type, which will be rejected by Flash Player.
Users of Shoutcast or a proxy-based Minicaster pro-ICE setup where the track data is served from a conventional webserver will normally have no issues, as their webserver will correctly identify the type for an XML file. If however the nowplaying data refuses to display, you should check that the content-type is valid by pointing your web browser directly at the nowplaying data URL, and using your browser's menu tools to check the header responses.
We cannot circumvent the new security features in Flash Player 9u3 either within Minicaster or as a patch, therefore the only option is to configure your Icecast server as above to ensure that an XML file is delivered with the correct content-type. The Icecast development team are aware of the issue and aim to close it in a future release. The KH development branch of Icecast is not affected, as it collects the mime.types file location from the configuration file where it can be changed to suit your system.
Draftlight, DNeX and the Draftlight logo are Trademarks of Draftlight Networks
©2002-2007 Draftlight Networks all rights reserved