-
Thomas B. Rücker authored
We are handling it the same as we would handle a SOURCE request. Due to legacy code, sender MUST send proper content-type header, if content type is not audio/mpeg! Can be tested using real-time encoded output and piping it into | curl -u username:password -H "Content-type: application/ogg" -T - http://localhost:8000/mountname.ogg Note that this example has ZERO timing, so a simple 'cat *.ogg' will fail. Whatever feeds the pipe must do it at proper timing for real-time playback! svn path=/icecast/trunk/icecast/; revision=18888
3c359b62