Icecast-Server issueshttps://gitlab.xiph.org/xiph/icecast-server/-/issues2019-01-03T16:34:53Zhttps://gitlab.xiph.org/xiph/icecast-server/-/issues/1878[PATCH] This patch adds the possibility to put full urls in the list of strea...2019-01-03T16:34:53ZPhilipp Schafft[PATCH] This patch adds the possibility to put full urls in the list of streams fetched from the master server.(reposted from IRC, cato in #icecast)
This patch adds the possibility to put full urls in the list of streams fetched from the master server. When pointing the <master-relay-*> options to a script instead of an icecast this allows to se...(reposted from IRC, cato in #icecast)
This patch adds the possibility to put full urls in the list of streams fetched from the master server. When pointing the <master-relay-*> options to a script instead of an icecast this allows to setup relays of arbitrary streams easily.Icecast 2.4.0Michael SmithMichael Smithhttps://gitlab.xiph.org/xiph/icecast-server/-/issues/663Icecast dump-file trigger2018-03-06T12:50:21Znaveed83Icecast dump-file triggericecast now has a setting named: <dump-file>/tmp/dump-example1.ogg</dump-file>
Is it possible that you in a later version make an admin trigger to enable/disable this feature. So u can specify when it shall start dumping, and when to s...icecast now has a setting named: <dump-file>/tmp/dump-example1.ogg</dump-file>
Is it possible that you in a later version make an admin trigger to enable/disable this feature. So u can specify when it shall start dumping, and when to stop instead of dumping the whole stream.
This is specially handy when u only need to record parts of your stream, like a live show instead of the whole stream which could take up loads of disk space.
regards,
^Naveed^Icecast 2.4.0Karl HeyesKarl Heyeshttps://gitlab.xiph.org/xiph/icecast-server/-/issues/1359[PATCH] <stream-name> config to completely override stream name2018-03-06T12:49:48Zrich_d_thomas[PATCH] <stream-name> config to completely override stream nameHi,
This enhancement request is as a result of discussion thread http://icecast.imux.net/viewtopic.php?t=5033
Please could the code be changed so that all aspects of the "stream name" is overwritten by the contents of the <stream-name>...Hi,
This enhancement request is as a result of discussion thread http://icecast.imux.net/viewtopic.php?t=5033
Please could the code be changed so that all aspects of the "stream name" is overwritten by the contents of the <stream-name> tag in the config.xml file.
Currently, <stream-name> sets what appears in the displayed status.xsl page. The stream name that appears in the listener's player is still what is set in the source client and not what is set in <stream-name>
Thank you.
rich_d_thomas@hotmail.com
Icecast 2.4.0Thomas B. RückerThomas B. Rückerhttps://gitlab.xiph.org/xiph/icecast-server/-/issues/1889Error pages needs update2018-03-06T12:49:48ZPhilipp SchafftError pages needs updateThe error pages generated by icecast are currently hardcoded. Some contain invalid HTML.
Please provide a valid but very simple HTML file for the HTTP errors 400 and 404. I will also take such error pages for 401 and 403 but that has le...The error pages generated by icecast are currently hardcoded. Some contain invalid HTML.
Please provide a valid but very simple HTML file for the HTTP errors 400 and 404. I will also take such error pages for 401 and 403 but that has less priority.
The pages (except for 401) all take an string telling the user about the error. Please just leave '%s' in the 'template' where it should go.
current pages look like this:
```
<b>%s</b>
```Icecast 2.4.0Thomas B. RückerThomas B. Rückerhttps://gitlab.xiph.org/xiph/icecast-server/-/issues/1916Fix & Verify proper escaping of HTTP related variables when e.g. printing to ...2018-03-06T12:49:48ZThomas B. RückerFix & Verify proper escaping of HTTP related variables when e.g. printing to access.logSee also initial report:
http://lists.xiph.org/pipermail/icecast/2012-December/012331.html
We should check escaping for all those variables printed to access.log .See also initial report:
http://lists.xiph.org/pipermail/icecast/2012-December/012331.html
We should check escaping for all those variables printed to access.log .Icecast 2.4.0Philipp SchafftPhilipp Schaffthttps://gitlab.xiph.org/xiph/icecast-server/-/issues/1870icecast should send 'expires' in all cases2018-03-06T12:49:48ZThomas B. Rückericecast should send 'expires' in all casescurrently it only sends it in a flash special case.
We should probably do this in all cases unless someone thinks it would break existing clients?currently it only sends it in a flash special case.
We should probably do this in all cases unless someone thinks it would break existing clients?Icecast 2.4.0Thomas B. RückerThomas B. Rückerhttps://gitlab.xiph.org/xiph/icecast-server/-/issues/1873[PATCH] icecast does not read arbitrary capitalized headers2018-03-06T12:49:48ZPhilipp Schafft[PATCH] icecast does not read arbitrary capitalized headers(Forwarded from cato on IRC because of #1871)
the YP-Interface does not work according to the http rfc. To be specific icecast does not read arbitrary capitalized headers from the answer as the standard says.
I have written my own impl...(Forwarded from cato on IRC because of #1871)
the YP-Interface does not work according to the http rfc. To be specific icecast does not read arbitrary capitalized headers from the answer as the standard says.
I have written my own implementation of the server-side yp-interface. when I return for example "Ypmessage: 1" instead of "YPMessage: 1" icecast doesn't find the header and the submission to my directory fails
Section 4.2 of RFC 2616 says: "Each header field consists of a name followed by a colon (":") and the field value. Field names are case-insensitive.
the error is in http://svn.xiph.org/icecast/trunk/icecast/src/yp.c in handle_returned_header(..) where instead of strncmp a case-insensitive comparison should be madeIcecast 2.4.0Thomas B. RückerThomas B. Rückerhttps://gitlab.xiph.org/xiph/icecast-server/-/issues/1942Spurious dots inside http request line logged to access log2018-03-06T12:49:48ZThomas B. RückerSpurious dots inside http request line logged to access log*"GET./status.xsl.HTTP/1.1"
vs
"GET /status.xsl HTTP/1.1"*"GET./status.xsl.HTTP/1.1"
vs
"GET /status.xsl HTTP/1.1"Icecast 2.4.0Philipp SchafftPhilipp Schafft