No need to use PHP. For the customer, all that matters is sending the appropriate type of content and the actual content. In this case, audio / mpeg (MP3) or OGG for Firefox (which now does not work for them, but it definitely can).
I suspect that they use PHP to relay the stream, is that they use SHOUTcast as a streaming server. While doing something, I found this: http://mp3stream.wfmu.org:8000/
Please note that when you click this URL in your browser, you get the main information page. However, if you click this on the music player, you will get a stream. The SHOUTcast server solves this based on the User-Agent string. If it contains "Mozilla" anywhere in the User-Agent, it returns this page. If this is not the case, it returns a stream. So, for the HTML5 audio player, it will use the browser user agent (which contains Mozilla) and will not be able to access the stream. I suspect their PHP script is what concerns the problem.
The PHP script will use cURL, connect to the streaming server with its own User-Agent (maybe anything if itβs not Mozilla), and pass the piece to the browser block that hit the PHP script. A piece of lime key.
Brad
source share