On 14 Feb 2020, at 21:46, Chip wrote:> > […] > > The second version 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-20150225150031Hi, you are using Icecast-kh, this is quite different from the „normal“ 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 (or rather, stop the „old“ one and start the „new“ one) so there will be a short downtime.> Many thanks for your help > > Chip
Thanks Marvin. On Fri, 14 Feb 2020 at 22:37, Marvin Scholz <epirat07 at gmail.com> wrote:> > Hi, > you are using Icecast-kh, this is quite different from the > „normal“ Icecast and we can not offer help for it, as we are > no familiar with it. >Ok, thanks. I see. [...] I assume thats probably because Icecast-kh 2.4 might have added HEAD> support? >Does icecast 2.4.4 not have HEAD support ? [...] You will eventually need to restart the Icecast server (or rather, stop> the „old“ one and start the „new“ one) so there will be a short downtime. >Thank you very much. I'll do this in a few hours time. All the best for now Chip -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.xiph.org/pipermail/icecast/attachments/20200214/27d9344f/attachment.html>
Good morning, On Fri, 2020-02-14 at 22:48 +0000, Chip wrote:> Thanks Marvin. > > On Fri, 14 Feb 2020 at 22:37, Marvin Scholz <epirat07 at gmail.com> wrote: > Does icecast 2.4.4 not have HEAD support ?No, official Icecast does not support HEAD requests as they are largely useless in Icecast context. HEAD requests are meant for cache validation. So they only apply to static files basically. For Icecast, beside a few boring files in web/ the answer to "is my copy still valid" is always "no". So by not supporting HEAD the client will retry with GET. Which... the client would need to do anyway IF we would reply with a positive status code for HEAD. Also (ab)using HEAD for monitoring is hardly useful: The stress to the server is the same for answering a non-stub* response to HEAD than to GET as in both cases the client must be attached to the source. Even a stub response ("endpoint exists" or "not found") would require most steps. It requires finding the endpoint, running its auth and applying its ACLs. That is more than half way thru the attach process. Hope that helps you. :) With best regards, * Non-stub results are hardly useful as HTTP is stateless anyway. The standard acknowledges that by making all information about the actual resource beside its existence optional. -- Philipp. (Rah of PH2)