Icecast Streaming Media Server

[m3gab0y]

Hello. Is it possible to (forcely) alter or disable the header, sent by Icecast, when a specific mountpoint is requested?

I want to pass via all firewalls, and one way is to alter the header, now if I request http://server:port/stream it sends back the stream with a nice "audio/mpeg" header and the firewall cuts me off
But if I try a shoutcast server for example, when I enforce to get my stream via http://server:port/; it serves back a stream with no header(s) at all.

I know I can alter this via proxy of somekind (web/local/etc), but I want to do this via the config. A good idea is the "<type>" tag and it will be really good if I can set whatever to send header or not and bypass all firewalls (except the really rare firewalls that are set to deny any server that is not sending header).

And last, but not least. I'm using your latest KH build and there is some weird bug on both Windows and Linux, that when a listener is listening, the metadata is not always updated on a song change.

Thanks for the time taken to read this and keep up the good work

[karlH]

I'm not sure what rules you would expect on that one, if you don't send audio/mpeg then what should you send and for which listeners? It sounds like a way to complicate things. You could try sending audio/ogg!

As for your bug report, I would need more info, like a version, logs etc

karl.

[m3gab0y]

My idea is NOT to send header! Just like a shoutcast server. And I want to do this, because many firewalls block out icecast's streams and don't touch shoutcast ones.

As for the bug, it's on Icecast KH23, and that's all I can see in my error.log:

[m3gab0y]

Actually i'm looking at the log and there is nothing weird and a new bug was found. When I specify a fallback mountpoint it works only if the listeners are connected to the stream and the source client disconnects. If a listener connects while the source is disconnected, it serves him a 404 code and not redirecting him to the fallback mount. The logs only confirm that icecast served a 404 error and no errors associated with it.

[karlH]

That is expected if you don't have a <limit-rate> set on any of the <mount> definitions falling back. The previous behaviour that you are expecting was an issue as the sending of file content was not throttled, with the setting the stream rate is kept sane when falling back.

The latest work is at www.icecast.pwp.blueyonder.co.uk/flv/ The feedback I have had from 23.7 looks to be ok for a kh24 release.

karl.