[Icecast] How to log querystring values?
phschafft at de.loewenfelsen.net
Tue May 8 05:51:50 UTC 2018
On Mon, 2018-05-07 at 09:09 -0300, subscription at nextdial.com.br wrote:
> Thanks so much for your time and relpy.
Haven't done much yet. :)
> This dawn, before read your email, I worked to implement the URL
> authentication and it worked like a charm. I am still using
> querystring instead of custom header field because I have no control
> over the player. But, the excelent news is, no more rproxy! =)
> And you were right, this way I have more possibilities than before!
It is. I really think that url auth is one of the best features we
have. :) It solves a lot of complicated problems nicely.
> Again, thanks so much and congrats for the awesome job.
> ps: Icecast is so far more efficient than SHOUTcast and a lot
> websites says they have no big differences, why?
I think it's because they run low-traffic streams. If your streaming
solution uses < 1% of the machine's resources, nobody cares.
That is different for those who push streams to thousands of listeners.
With best regards,
> De: "Philipp Schafft" <phschafft at de.loewenfelsen.net>
> Enviado: segunda-feira, 7 de maio de 2018 03:40
> Para: subscription at nextdial.com.br, "Icecast streaming server user discussions" <icecast at xiph.org>
> Assunto: Re: [Icecast] How to log querystring values?
> Good Morning Thiago,
> On Sun, 2018-05-06 at 10:23 -0300, subscription at nextdial.com.br wrote:
> > Dear Philipp,
> > Thanks for you reply.
> > My goal is to show in our analytics page segmented data (official apps,
> > partner apps, third-party apps, demographic and geo).
> > To do so each app pass some values in the query string (ie: app id,
> > user id, lat, lng). And I need to know those values in order to do
> > that.
> I would recommend to add those to (a) custom header field(s). You can
> then log that by using URL auth. This is to the standards and will also
> add more flexibility to the system, such as real time stats.
> If you really, really need to pass the parameters using query string
> parameters we could implement a separate logfile for that. That would
> keep the main log intact and provide a (probably better) parseable log
> for those data. (If you're interested in this option contact me
> > Today we are using nginx as a reverse proxy to Icecast to get those data
> > but it double the cpu/mem usage =(
> using a rproxy is not ideal and should be avoided. :)
> with best regards,
> > ----------------------------------------
> > De: "Philipp Schafft" <lion at lion.leolix.org>
> > Enviado: domingo, 6 de maio de 2018 09:30
> > Para: subscription at nextdial.com.br, "Icecast streaming server user
> > discussions" <icecast at xiph.org>
> > Assunto: Re: [Icecast] How to log querystring values?
> > Dear Mr./Ms. subscription,
> > On Sun, 2018-05-06 at 08:35 -0300, subscription at nextdial.com.br wrote:
> > > I need to get some values passed in the querystring request in the log
> > > file.
> > >
> > > Something like that bellow:
> > >
> > > ie: "GET /radio?id=1 HTTP/1.1" instead of only "GET /radio HTTP/1.1"
> > >
> > > Do I need to change something in the source and compile? Or there is
> > > another way?
> > What exactly is your goal? Maybe you can give us a bit of an
> > understanding of the context.
> > Query parameters are to be interpreted by the server, in this case
> > Icecast, not external software. Therefore I suspect that there is a
> > better solution for your problem.
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:
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 490 bytes
Desc: This is a digitally signed message part
More information about the Icecast