| View previous topic :: View next topic |
| Author |
Message |
mxb
Joined: 28 Nov 2008 Posts: 5
|
Posted: Fri Nov 27, 2009 5:50 pm Post subject: Wget HEAD request problem |
|
|
I`m currently writing a script to regularly check for new mount points on icecast2. But while using wget with the --spider switch (HEAD request), I`ve noticed the response from the server is always 400 Bad Request. This is the case for all urls used, even the index page.
For the script to work I`m looking for 200 OK which is expected. Is this a bug or is it normal behaviour for icecast. Also is there anything I can do about it ?
-
Alternatively I could use <on-connect> feature for the end result (start streamTranscoder when a source connects to a specific mount point) but it fails to start a bash script when the source connects. I`ve tested the script successfully under the same user that icecast runs.
Is there anyknown problems with on-connect on the build of icecast i`m using ? If not I`ll post my icecast config here.
| ubuntuserver 8.04 LTS / Icecast 2.3.2-kh18 | |
|
| Back to top |
|
 |
karlH Code Warrior

Joined: 13 Jun 2005 Posts: 5476 Location: UK
|
Posted: Fri Nov 27, 2009 6:42 pm Post subject: |
|
|
The HEAD method has never been handled, there hasn't been any call for it. There is also a question of the correct behaviour in certain cases such as fallback and on-demand relaying. You could get N bytes or 1 second worth of the stream if you wish to check for the stream, or use say /status.xsl?mount=/mystream or even use the stats interface curl -X STATS http://admin:pw@host:port/
The run on-connect program at stream start should be working fine on the setup you have specified. Are you not seeing any attempt in the error log?
karl. |
|
| Back to top |
|
 |
mxb
Joined: 28 Nov 2008 Posts: 5
|
Posted: Sat Nov 28, 2009 10:34 am Post subject: |
|
|
thanks for your reply.
I`ve eventually got on-connect working by moving the script to the users home dir that icecast runs on. |
|
| Back to top |
|
 |
|