The one place for your designs
To enable design management, you'll need to meet the requirements. If you need help, reach out to our support team for assistance.
Server does not move new listeners to fallback source if specified via HTTP request
Icecast server 2.3.1 in Debian Etch
Server does not move new listeners to fallback source if specified via HTTP request. I have two examples of this not functioning as expected:
-
Listeners are connected to a mountpoint named "/". "/" has no fallback defined in server XML. An HTTP request to define a fallback is issued, in my case it looks like this: http://ash.rockingtiger.com:8000/admin/fallbacks?mount=/&fallback=/live-1.mp3 When source disconnects, current listeners are moved to "/live-1.mp3" as expected. When a new listener connects to "/" the client (in this case iTunes) is given a 404. My expectation was the new clients that connect to "/" be moved to "/live-1.mp3" the same way the old clients were moved.
-
Listeners are connected to "/". "/" has a fallback of "/live-2.mp3" defined. An HTTP request to define a fallback is issued, in my case it looks like this: http://ash.rockingtiger.com:8000/admin/fallbacks?mount=/&fallback=/live-1.mp3 When source disconnects, current listeners are moved to "/live-1.mp3" as expected. New clients that connect to "/" are moved to "/live-2.mp3", not "/live-1.mp3" as expected.