View previous topic :: View next topic |
Author |
Message |
chris
Joined: 13 Jun 2012 Posts: 15
|
Posted: Tue May 07, 2013 7:29 am Post subject: Header problem: ICY 200 OK |
|
|
Hi Karl
Sorry im bothering you again. I have now installed Icecast 2.3.3-kh7-41 and it seems to work good. The only problem i am seeing is that it is now responding with ICY 200 OK instead of HTTP/1.0 200 OK. I am serving playlistfiles (asx) and it looks like this icy-200 causes a problem within Windows Media player.
Have you heard something similar already?
thanks
chris |
|
Back to top |
|
|
karlH Code Warrior
Joined: 13 Jun 2005 Posts: 5476 Location: UK
|
Posted: Tue May 07, 2013 2:34 pm Post subject: |
|
|
I have had previous reports indicating that the ICY was required for the stream which is why that is the default for that.
You can override that by appending to the stream url like
/mountpoint?_hdr=0
the default for that player is 1 which may be required for earlier versions, see if that makes playback work, it may just be an issue if started from an asx.
karl. |
|
Back to top |
|
|
chris
Joined: 13 Jun 2012 Posts: 15
|
Posted: Wed May 08, 2013 12:30 pm Post subject: :!: possible bug with delivery of static files |
|
|
I think i just found a bug!
I serve playlist-files from the icecast-servers. If the user-agent "Windows-Media-Player/12.0.7601.17514" tries to fetch one of these files, i get the following lines as HTTP-Data (not header!!). Because of that, the player will not start playing. I tried your _hdr=0 which works, but imho this data should not be sent when a static file gets served?!
Chris
curl http://10.2.3.4/rsc_de/mp3_128.asx -v -A "Windows-Media-Player/12.0.7601.17514"
* About to connect() to 10.2.3.4 port 80 (#0)
* Trying 10.2.3.4... connected
* Connected to 10.2.3.4 (10.2.3.4) port 80 (#0)
> GET /rsc_de/mp3_128.asx HTTP/1.1
> User-Agent: Windows-Media-Player/12.0.7601.17514
> Host: 10.2.3.4
> Accept: */*
>
ICY 200 OK
Content-Length: 175
Content-Type: video/x-ms-asf
Server: Icecast 2.3.3-kh7
Cache-Control: no-cache
Pragma: no-cache
Expires: Mon, 26 Jul 1997 05:00:00 GMT
<asx version="3.0">
<entry>
<ref href="http://10.2.3.4/m/rsc_de/mp3_128" />
</entry>
<entry>
<ref href="http://10.2.3.4/m/rsc_de/mp3_128" />
</entry>
</asx>
* Connection #0 to host 10.2.3.4 left intact
* Closing connection #0 |
|
Back to top |
|
|
karlH Code Warrior
Joined: 13 Jun 2005 Posts: 5476 Location: UK
|
Posted: Wed May 08, 2013 1:32 pm Post subject: |
|
|
The problem was that without the ICY, the effect was that the stream did not start playback. This may of been fixed now in wmp, if you are saying that streams playback no problem in wmp with _hdr=0 for both mp3 and aac[+]] then I can remove the predefined value.
karl. |
|
Back to top |
|
|
chris
Joined: 13 Jun 2012 Posts: 15
|
Posted: Wed May 08, 2013 1:43 pm Post subject: |
|
|
Thank you for your fast reply!
I just tested it, with my WMP V12.0.76 (Windows 7), it plays regardless _hdr=0. But you might keep this feature.
The problem here is that even files (static playlistfiles) contain header-infos in the body. If you can see this in action here: http://193.218.104.241/drs3/mp3_128.asx?_hdr=1
If you save this file, VLC will play it (it's error handling seems to be better), but WMP says nope!
As a workaround i tried to close a xml-comment (" --!> ") before my content, but it does not accept it as well.
Is there a possibility to apply the hdr=1 / ICY 200-thing only to streams but not to static asx-files?
Thanks
Chris |
|
Back to top |
|
|
karlH Code Warrior
Joined: 13 Jun 2005 Posts: 5476 Location: UK
|
Posted: Wed May 08, 2013 5:24 pm Post subject: |
|
|
I can do http response on file requests which is what the asx would be, leaving icy on streams only for wmp useragents.
This is now done in github, I can do a windows build if people really want it, I just don't do them that frequently.
karl. |
|
Back to top |
|
|
|