Icecast dev - Aug 2004 - AW: Howto recieve a header or something for icecaststations

Hi,

Sorry for my newbie question, but I can not find it documented anywhere and
I am too lazy to browse other peoples code :-).
I want to implement shoutcast/icecast listening support for my app. It did
not seem to be any problem with shoutcast, but playing around with some
icecast stations tonight I found that I am not able to receive any plaintext
headers when first opening a stream. Some ogg stations present metainfo in
the ogg format when connecting with which is fine for me, but some stations
do not present any info at all. They start with the raw mp3 or ogg data. No
header nothing. So can you please advice me what I am doing wrong? Is there
a special request I need to send to get something like a header from the
icecast server? Is there a document that explains the client request
handling? Thank you and regards 

<p>--- >8 ----
List archives:  http://www.xiph.org/archives/
icecast project homepage: http://www.icecast.org/
To unsubscribe from this list, send a message to
'icecast-dev-request@xiph.org'
containing only the word 'unsubscribe' in the body.  No subject is
needed.
Unsubscribe messages sent to the list will be ignored/filtered.

At 04:20 PM 4/14/2004, you wrote:
>Hi,
>
>Sorry for my newbie question, but I can not find it documented anywhere and
>I am too lazy to browse other peoples code :-).
>I want to implement shoutcast/icecast listening support for my app. It did
>not seem to be any problem with shoutcast, but playing around with some
>icecast stations tonight I found that I am not able to receive any plaintext
>headers when first opening a stream. Some ogg stations present metainfo in
>the ogg format when connecting with which is fine for me, but some stations
>do not present any info at all. They start with the raw mp3 or ogg data. No
>header nothing. So can you please advice me what I am doing wrong? Is there
>a special request I need to send to get something like a header from the
>icecast server? Is there a document that explains the client request
>handling? Thank you and regards
icecast will keep track of the HTTP headers sent by the source encoder on 
initial connection.  These headers usually contain the icy-* ice-* headers 
that provide information about the stream.  I suppose it's possible for a 
source encoder to NOT send any headers, and thus no stream headers would be 
sent to connected listening clients...although I thought at LEAST the 
Server: HTTP response header should be sent with every request....and also 
the Content-type header should also be sent...Are you SURE the servers your 
connecting to are icecast servers ? if so, give us some examples...

oddsock

<p>>--- >8 ----
>List archives:  http://www.xiph.org/archives/
>icecast project homepage: http://www.icecast.org/
>To unsubscribe from this list, send a message to 
>'icecast-dev-request@xiph.org'
>containing only the word 'unsubscribe' in the body.  No subject is
needed.
>Unsubscribe messages sent to the list will be ignored/filtered.
<p>--- >8 ----
List archives:  http://www.xiph.org/archives/
icecast project homepage: http://www.icecast.org/
To unsubscribe from this list, send a message to
'icecast-dev-request@xiph.org'
containing only the word 'unsubscribe' in the body.  No subject is
needed.
Unsubscribe messages sent to the list will be ignored/filtered.

>You will always receive HTTP headers when you connect, never just the raw 
>bitstream. Perhaps you're doing something else wrong - 
Oddsock, Mike,

Thank you. I was the fool (maybe not enough sleep:-). Because the shoutcast
servers at shoutcast.com never sent any useful data in the "real" http
header I just threw it away and always looked at the following data (where
shoutcast sends plain text stream info). Icecast sends the info in the http
header itself.Ahh... Now I got it.
Regards
Frank

<p>--- >8 ----
List archives:  http://www.xiph.org/archives/
icecast project homepage: http://www.icecast.org/
To unsubscribe from this list, send a message to
'icecast-dev-request@xiph.org'
containing only the word 'unsubscribe' in the body.  No subject is
needed.
Unsubscribe messages sent to the list will be ignored/filtered.

On Thursday 15 April 2004 07:20, Frank wrote:
> Hi,
>
> Sorry for my newbie question, but I can not find it documented anywhere and
> I am too lazy to browse other peoples code :-).
> I want to implement shoutcast/icecast listening support for my app. It did
> not seem to be any problem with shoutcast, but playing around with some
> icecast stations tonight I found that I am not able to receive any
> plaintext headers when first opening a stream. Some ogg stations present
> metainfo in the ogg format when connecting with which is fine for me, but
> some stations do not present any info at all. They start with the raw mp3
> or ogg data. No header nothing. So can you please advice me what I am doing
> wrong? Is there a special request I need to send to get something like a
> header from the icecast server? Is there a document that explains the
> client request handling? Thank you and regards
>
You will always receive HTTP headers when you connect, never just the raw 
bitstream. Perhaps you're doing something else wrong - icecast cannot ever
do
this.

For listening clients, icecast is pure HTTP - you don't need any special 
protocol support.

Mike

--- >8 ----
List archives:  http://www.xiph.org/archives/
icecast project homepage: http://www.icecast.org/
To unsubscribe from this list, send a message to
'icecast-dev-request@xiph.org'
containing only the word 'unsubscribe' in the body.  No subject is
needed.
Unsubscribe messages sent to the list will be ignored/filtered.