Displaying 9 results from an estimated 9 matches for "jorr".
Did you mean:
joro
2020 Sep 22
2
Listener stats
....
Why not just use the API? Remove the ".xsl" from any URL in the admin
interface and get the raw XML. The rendered webinterface is just that:
XSLT applied to the API.
> This should be easy.
As easy as asking nicely.
With best regards,
> > On Sep 22, 2020, at 11:16 AM, <jorr at streamguys.com> <jorr at streamguys.com> wrote:
> >
> > What about scrapping the access logs for connections that have completed, or utilizing netstat outputs to get active listeners (minus sources)?
> >
> > Either of those options would get you remote IP addre...
2020 Sep 22
1
Listener stats
...get the raw XML. The rendered webinterface is just that:
>> XSLT applied to the API.
>>
>>> This should be easy.
>>
>> As easy as asking nicely.
>>
>>
>> With best regards,
>>
>>
>>>> On Sep 22, 2020, at 11:16 AM, <jorr at streamguys.com> <jorr at streamguys.com> wrote:
>>>>
>>>> What about scrapping the access logs for connections that have completed, or utilizing netstat outputs to get active listeners (minus sources)?
>>>>
>>>> Either of those options w...
2020 Sep 22
2
Listener stats
What about scrapping the access logs for connections that have completed, or utilizing netstat outputs to get active listeners (minus sources)?
Either of those options would get you remote IP addresses, both a slightly different view in that logs are after a connection closes, while netstat is while the connection is open.
-----Original Message-----
From: Icecast-dev <icecast-dev-bounces at
2020 Sep 22
0
Listener stats
...should be able to get a Json or XML file with this in it. The reason I need this is to show current listeners and from where they are listening. I do this with the other streaming software without any modifications or adjustments. This should be easy.
Reaz
> On Sep 22, 2020, at 11:16 AM, <jorr at streamguys.com> <jorr at streamguys.com> wrote:
>
> What about scrapping the access logs for connections that have completed, or utilizing netstat outputs to get active listeners (minus sources)?
>
> Either of those options would get you remote IP addresses, both a slightl...
2016 Jul 27
2
Proxy
Hi all,
I want to do a proxy to icecast (:8000) with nginx (:80).
Its working for me, stream is running on port 80, but on the first loading
is "pending" For a long time before its starts play.
Who using the "proxy_pass" on nginx and can help?
Thnx.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
2020 Sep 22
0
Listener stats
...from any URL in the admin
> interface and get the raw XML. The rendered webinterface is just that:
> XSLT applied to the API.
>
>> This should be easy.
>
> As easy as asking nicely.
>
>
> With best regards,
>
>
>>> On Sep 22, 2020, at 11:16 AM, <jorr at streamguys.com> <jorr at streamguys.com> wrote:
>>>
>>> What about scrapping the access logs for connections that have completed, or utilizing netstat outputs to get active listeners (minus sources)?
>>>
>>> Either of those options would get you rem...
2016 Jul 27
2
Proxy
...//127.0.0.1:8000/stream1;
And one more thing,
the proxy passing the user agent of the listener and I can see that on the
icecast dashboard,
But I can't see the IP address.for several hours im trying with the nginx
documentation but without ant success.
Thanks in advance.
From: jorr at streamguys.com [mailto:jorr at streamguys.com]
Sent: Wednesday, July 27, 2016 6:48 PM
To: 'Yaniv Sharon'; icecast-dev at xiph.org
Subject: RE: [Icecast-dev] Proxy
We've tested this as working relatively well, disable buffering is the major
key if I recall. Otherwise the NGINX se...
2020 Sep 21
2
Listener stats
Hello Jordan
Thanks for the reply. I commented out all the fields in the
status-json.xsl but it didn't give me the listener IP. The example
below would show me the source IP. I can get the IP from the web
interface at this location,
http://xxx.xxx.xxx.xxx:8000/admin/listclients.xsl?mount=/dhantal, but
that means I would have to scrape the web interface which I don't want
to do.
2016 Jul 27
0
Proxy
We've tested this as working relatively well, disable buffering is the major
key if I recall. Otherwise the NGINX server loads up data before handing off
to the client.
server {
listen 80;
server_name my_dns_name.tldn;
location / {
proxy_buffering off;
proxy_ignore_client_abort off;
proxy_intercept_errors on;