[Icecast] dynamic source creation?

[uno]

"Thomas B. Rücker":
> >>>> You can combine this with: default mount
> >>>> https://trac.xiph.org/ticket/1914#comment:1
> >>>> Start with <mount type="default">

dynamic mountpoints:

question is how do they co-exists at all with static ones.
the default mount catches all source clients on connect, which makes
some sense if default means "*" and order in the conf doesn't matter. 
(tested with an on-connect script in the default mount section):

	<!-- some static mounts -->
	<mount>
		<mount-name>/s1</mount-name>
		 <authentication type="url">
			...
		 </authentication>
		...
	</mount>
	<mount>
		<mount-name>/s2</mount-name>
                <password>***</password>
		...
	</mount>
	<!-- dyn -->
        <mount type="default">
                <password>***</password>
                <on-connect>/path/to/on_connect.php</on-connect>
                <on-disconnect>/path/to/on_disconnect.php</on-disconnect>
		...
        </mount>

so if a client connects on e.g. /s1, the script within the default section
is executed, url auth doensn't work anymore.

instead of a default, a regex- or wildcard pattern would make sense, imho.
something like <mount-name>/dyn-*</mount-name>

or is the dynamic default mount meant to be the only one in an icecast config?


> If putting a space at the beginning of a mount name confuses things to a
> degree where it affects other things/users/streams on the server, then
> we should look into it though. Could you provide actual examples of
> mount point names, what you did and what happened?


source client is butt 0.1.13, mountpoint set in butt is " source" w/o quotes.
server is Icecast 2.4.0

butt failes to connect, and seems to try desperately, that's how i interpret
the logs. but aside from filling the logs, nothing special happened, i.e.
the server kept doing its job. 

...
[2014-09-26  11:59:06] DBUG stats/modify_node_event update global clients (3)
[2014-09-26  11:59:06] DBUG stats/modify_node_event update global clients (4)
[2014-09-26  11:59:06] DBUG stats/modify_node_event update global connections (297)
[2014-09-26  11:59:06] DBUG stats/modify_node_event update global clients (3)
[2014-09-26  11:59:06] EROR connection/_handle_connection HTTP request parsing failed
[2014-09-26  11:59:06] EROR connection/_handle_connection HTTP request parsing failed
[2014-09-26  11:59:06] DBUG stats/modify_node_event update global clients (4)
[2014-09-26  11:59:06] DBUG stats/modify_node_event update global connections (298)
[2014-09-26  11:59:06] DBUG stats/modify_node_event update global clients (3)
[2014-09-26  11:59:06] DBUG stats/modify_node_event update global clients (4)
[2014-09-26  11:59:06] DBUG stats/modify_node_event update global connections (299)
[2014-09-26  11:59:06] DBUG stats/modify_node_event update global clients (3)
[2014-09-26  11:59:06] EROR connection/_handle_connection HTTP request parsing failed
[2014-09-26  11:59:06] DBUG stats/modify_node_event update global clients (4)
[2014-09-26  11:59:06] DBUG stats/modify_node_event update global connections (300)
[2014-09-26  11:59:06] DBUG stats/modify_node_event update global clients (3)
[2014-09-26  11:59:06] DBUG stats/modify_node_event update global clients (4)
[2014-09-26  11:59:06] DBUG stats/modify_node_event update global connections (301)
[2014-09-26  11:59:06] EROR connection/_handle_connection HTTP request parsing failed
[2014-09-26  11:59:06] EROR connection/_handle_connection HTTP request parsing failed
...

cheers, u.