Apologies for posting an "issue" here, just not quite sure where else to post a question (suggestions gratefully received).
I'm trying to disable most public-facing Icecast web-pages, and have figured that I can likely do this by putting everything behind a wildcard mount that then points to my auth script using Icecast's http auth method.
I would still like to be able to access Icecast's admin panel, via my admin user/pass however.
I have kludged this together using the following mount point.
Seems like there should be a more elegant way of doing this though, and I've read in the Icecast-KH "news" docs about "ban/allow files".
Can someone point me in the right direction? I've heard suggestions of just deleting some of the files in /web but I don't want to break anything and also rely on status-json.XSL for some of my functionality.
Hi,
Apologies for posting an "issue" here, just not quite sure where else to post a question (suggestions gratefully received).
I'm trying to disable most public-facing Icecast web-pages, and have figured that I can likely do this by putting everything behind a wildcard mount that then points to my auth script using Icecast's http auth method.
I would still like to be able to access Icecast's admin panel, via my admin user/pass however.
I have kludged this together using the following mount point.
<mount-name>/*[!'admin.html', !'adminbar.html', !'style.css', !'images/corner_topright.jpg', !'images/corner_topleft.jpg', !'images/corner_bottomright.jpg', !'images/corner_bottomleft.jpg', !'images/key.png']*</mount-name>Seems like there should be a more elegant way of doing this though, and I've read in the Icecast-KH "news" docs about "ban/allow files".
Can someone point me in the right direction? I've heard suggestions of just deleting some of the files in /web but I don't want to break anything and also rely on status-json.XSL for some of my functionality.
Many thanks!