Displaying 4 results from an estimated 4 matches for "_high_".
2014 May 23
3
Icecast2, ezstream and reverse proxy
Hello,
Correct me if I'm wrong, but what you get from Icecast *is* HTTP.
Anyway, we use proxying because on our server, some of our clients
cannot connect to port 8000 without bypassing their company firewall,
and we don't have the possibility to add another public IP. So with
Apache, here is what we do :
########################################################################
#
#
2014 May 23
1
Icecast2, ezstream and reverse proxy
...to make icecast bind to port 80.
>
>> and we don't have the possibility to add another public IP.
>
> That sucks, but is not an Icecast problem, dirty workarounds ensue.
>
>> So with
>> Apache, here is what we do :
> <snip />
> Make sure you have a _high_ number of MaxClients or your Apache will
> throw a fit after the first few listeners connect and not serve your
> websites anymore.
> Also Apache is not that great at handling many long-lived connections.
> If you really know how to set up an high performance reverse proxy, you
> won...
2014 May 23
0
Icecast2, ezstream and reverse proxy
...any firewall,
The preferred method here is to make icecast bind to port 80.
> and we don't have the possibility to add another public IP.
That sucks, but is not an Icecast problem, dirty workarounds ensue.
> So with
> Apache, here is what we do :
<snip />
Make sure you have a _high_ number of MaxClients or your Apache will
throw a fit after the first few listeners connect and not serve your
websites anymore.
Also Apache is not that great at handling many long-lived connections.
If you really know how to set up an high performance reverse proxy, you
won't have to ask how to...
2014 May 23
1
Icecast2, ezstream and reverse proxy
...another public IP.
> That sucks, but is not an Icecast problem, dirty workarounds ensue.
It's true. I never said it was an Icecast problem. This is just a recipe
for a dirty workaround.
>
>> So with
>> Apache, here is what we do :
> <snip />
> Make sure you have a _high_ number of MaxClients or your Apache will
> throw a fit after the first few listeners connect and not serve your
> websites anymore.
> Also Apache is not that great at handling many long-lived connections.
> If you really know how to set up an high performance reverse proxy, you
> won...