Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • Icecast-Server Icecast-Server
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 102
    • Issues 102
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 5
    • Merge requests 5
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • External wiki
    • External wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Xiph.Org
  • Icecast-ServerIcecast-Server
  • Issues
  • #1309
Closed
Open
Created Feb 26, 2008 by lee@lee

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:

  1. 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.

  2. 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.

Assignee
Assign to
Time tracking