[Icecast] Custom HTTP auth headers

Philipp Schafft phschafft at de.loewenfelsen.net
Tue May 28 09:49:48 UTC 2019

Good morning,

On Mon, 2019-05-27 at 22:09 -0700, Thiago Sousa Santos wrote:
> Hello,
> I'd like to have my icecast client (libshout based) that would use the HTTP
> header:
> "Authorization: bearer <token>"
> as its authentication method. I didn't find documentation on how to do it,
> also couldn't find anything like that in libshout source code. Is this
> possible in the current code?


> Additionally, if not possible, is this feature something interesting to
> have at libshout or should I use something else?

I actually thought about it several times the last year. However it has
not proven very useful to an Icecast based system because RFC 6750 which
defines it is missing a very important point: There is no way to inform
the client about the token. It is always transferred via a side channel
(from the HTTP perspective).

This not-so-little details renders it mostly useless in my opinion.

I wonder, why do you want it? No official Icecast can work with it

Also feel free to join us for a little chat about it on IRC:

With best regards,

Philipp Schafft (CEO/Geschäftsführer) 
Telephon: +49.3535 490 17 92

Löwenfelsen UG (haftungsbeschränkt)     Registration number:
Bickinger Straße 21                     HRB 12308 CB
04916 Herzberg (Elster)                 VATIN/USt-ID:
Germany                                 DE305133015
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 490 bytes
Desc: This is a digitally signed message part
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20190528/527965d0/attachment.sig>

More information about the Icecast mailing list