search for: gc6e5d83

Hi I'm clutching at straws here. I have a user who requires access to a status-json.xsl to publish now playing data for an Alexa skill and this can be accessed via a browser at: - http://example.com:8000/status-json.xsl He says that now his PHP script cannot access the file. I know that Alexa requires *streams* to be served over https but this has previously worked and his skill is

...ersion above works because Icecast is configured differently to the first example - indeed, they're different versions: This doesn't work: [chip at machine]# icecast -v Icecast 2.3.3-kh11-20150225150031 This one works with curl nicely: [chip at machine2]# icecast -v Icecast 2.4.0-kh12-8-gc6e5d83 How easy is it to upgrade Icecast mid-flight on a production server? Can it be done seamlessly or what sort of downtime am I looking at? Many thanks for your help Chip -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.xiph.org/pipermail/icecast/atta...

...Icecast and we can not offer help for it, as we are no familiar with it. You might want to either switch to the „official“ Icecast or maybe file a bug with the Icecast-kh project instead. > > This one works with curl nicely: > > [chip at machine2]# icecast -v > Icecast 2.4.0-kh12-8-gc6e5d83 > I assume thats probably because Icecast-kh 2.4 might have added HEAD support? > How easy is it to upgrade Icecast mid-flight on a production server? > Can it > be done seamlessly or what sort of downtime am I looking at? > You will eventually need to restart the Icecast server...