Klaas Jan Wierenga
2005-Jun-22 23:07 UTC
[Icecast] running icecast and a webserver on same port
Hi, You can if your machine is assigned two IP addresses. Then you can bind the webserver to port 80 on the first IP-adres and bind icecast to port 80 on the second IP-address. Hope this is helpful. Regards, KJ -----Oorspronkelijk bericht----- Van: icecast-bounces@xiph.org [mailto:icecast-bounces@xiph.org]Namens Laust Brock-Nannestad Verzonden: woensdag 22 juni 2005 2:27 Aan: icecast@xiph.org Onderwerp: Re: [Icecast] running icecast and a webserver on same port On Wed, 22 Jun 2005, Saul Qui?ones wrote:> Hi all!! Does anyone know if you can have your > web server running on port 80 and also icecast on the > same port in a easy way??. Thanks in advance!!You can't run both on the same port, but you can pass the stream through a a CGI script - from Icecast (running on the normal port 8000 for example) and on to listeners connecting to the web server on port 80. It's not without some problems, though: 1. Some web servers (like Apache 1.3) _always_ add headers to the output of CGI scripts, so you don't get a "clean" copy of Icecast's output. Certain players don't mind the extra headers (foobar2000 on Windows, and ogg123), but others (Winamp and Windows Media Player) get confused and will refuse to play the stream. With other web servers (thttpd is one I've tried) that don't add any headers to the output of CGI scripts, it seems to work quite well, however. 2. Since traffic on port 80 is sometimes proxied/cached (based on the assumption that it's normal web traffic) at the other end, there's a chance you'll have proxies taking up connections on your server even after the actual listener has disconnected. 3. Performance probably isn't so great, but this shouldn't be a concern unless you have many listeners. If this hasn't discouraged you from trying, the "webamp" Perl script mentioned in the following article makes a suitable pass-thru CGI script with minor modifications: http://www.perlfect.com/articles/streaming.shtml Regards, Laust _______________________________________________ Icecast mailing list Icecast@xiph.org http://lists.xiph.org/mailman/listinfo/icecast
Care to shed some light on this? I have about 10 IPs that are at my disposal and 3 I've been keeping for spares and whatnot. Though binding them is a little beyond me. TIA Justin On 6/22/05, Klaas Jan Wierenga <k.j.wierenga@home.nl> wrote:> > Hi, > > You can if your machine is assigned two IP addresses. Then you can bind the > webserver to port 80 on the first IP-adres and bind icecast to port 80 on > the second IP-address. > > Hope this is helpful. > > Regards, > KJ > > -----Oorspronkelijk bericht----- > Van: icecast-bounces@xiph.org [mailto:icecast-bounces@xiph.org]Namens > Laust Brock-Nannestad > Verzonden: woensdag 22 juni 2005 2:27 > Aan: icecast@xiph.org > Onderwerp: Re: [Icecast] running icecast and a webserver on same port > > > On Wed, 22 Jun 2005, Saul Qui?ones wrote: > > > Hi all!! Does anyone know if you can have your > > web server running on port 80 and also icecast on the > > same port in a easy way??. Thanks in advance!! > > You can't run both on the same port, but you can pass the stream through a > a CGI script - from Icecast (running on the normal port 8000 for example) > and on to listeners connecting to the web server on port 80. It's not > without some problems, though: > > 1. Some web servers (like Apache 1.3) _always_ add headers to the output > of CGI scripts, so you don't get a "clean" copy of Icecast's output. > Certain players don't mind the extra headers (foobar2000 on Windows, and > ogg123), but others (Winamp and Windows Media Player) get confused and > will refuse to play the stream. With other web servers (thttpd is one I've > tried) that don't add any headers to the output of CGI scripts, it seems > to work quite well, however. > > 2. Since traffic on port 80 is sometimes proxied/cached (based on the > assumption that it's normal web traffic) at the other end, there's a > chance you'll have proxies taking up connections on your server even after > the actual listener has disconnected. > > 3. Performance probably isn't so great, but this shouldn't be a concern > unless you have many listeners. > > If this hasn't discouraged you from trying, the "webamp" Perl script > mentioned in the following article makes a suitable pass-thru CGI script > with minor modifications: > > http://www.perlfect.com/articles/streaming.shtml > > > Regards, > > Laust > > > > _______________________________________________ > Icecast mailing list > Icecast@xiph.org > http://lists.xiph.org/mailman/listinfo/icecast > > _______________________________________________ > Icecast mailing list > Icecast@xiph.org > http://lists.xiph.org/mailman/listinfo/icecast >
Geoff Staples
2005-Jun-26 11:14 UTC
[Icecast] running icecast and a webserver on same port
I'm curious about why you would want to run Icecast on port 80. Geoff Justin Bot wrote:>Care to shed some light on this? I have about 10 IPs that are at my >disposal and 3 I've been keeping for spares and whatnot. Though >binding them is a little beyond me. > >TIA > >Justin > >On 6/22/05, Klaas Jan Wierenga <k.j.wierenga@home.nl> wrote: > > >>Hi, >> >>You can if your machine is assigned two IP addresses. Then you can bind the >>webserver to port 80 on the first IP-adres and bind icecast to port 80 on >>the second IP-address. >> >>Hope this is helpful. >> >>Regards, >>KJ >> >>-----Oorspronkelijk bericht----- >>Van: icecast-bounces@xiph.org [mailto:icecast-bounces@xiph.org]Namens >>Laust Brock-Nannestad >>Verzonden: woensdag 22 juni 2005 2:27 >>Aan: icecast@xiph.org >>Onderwerp: Re: [Icecast] running icecast and a webserver on same port >> >> >>On Wed, 22 Jun 2005, Saul Qui?ones wrote: >> >> >> >>>Hi all!! Does anyone know if you can have your >>>web server running on port 80 and also icecast on the >>>same port in a easy way??. Thanks in advance!! >>> >>> >>You can't run both on the same port, but you can pass the stream through a >>a CGI script - from Icecast (running on the normal port 8000 for example) >>and on to listeners connecting to the web server on port 80. It's not >>without some problems, though: >> >>1. Some web servers (like Apache 1.3) _always_ add headers to the output >>of CGI scripts, so you don't get a "clean" copy of Icecast's output. >>Certain players don't mind the extra headers (foobar2000 on Windows, and >>ogg123), but others (Winamp and Windows Media Player) get confused and >>will refuse to play the stream. With other web servers (thttpd is one I've >>tried) that don't add any headers to the output of CGI scripts, it seems >>to work quite well, however. >> >>2. Since traffic on port 80 is sometimes proxied/cached (based on the >>assumption that it's normal web traffic) at the other end, there's a >>chance you'll have proxies taking up connections on your server even after >>the actual listener has disconnected. >> >>3. Performance probably isn't so great, but this shouldn't be a concern >>unless you have many listeners. >> >>If this hasn't discouraged you from trying, the "webamp" Perl script >>mentioned in the following article makes a suitable pass-thru CGI script >>with minor modifications: >> >>http://www.perlfect.com/articles/streaming.shtml >> >> >>Regards, >> >>Laust >> >> >> >>_______________________________________________ >>Icecast mailing list >>Icecast@xiph.org >>http://lists.xiph.org/mailman/listinfo/icecast >> >>_______________________________________________ >>Icecast mailing list >>Icecast@xiph.org >>http://lists.xiph.org/mailman/listinfo/icecast >> >> >> >_______________________________________________ >Icecast mailing list >Icecast@xiph.org >http://lists.xiph.org/mailman/listinfo/icecast > > > > > >-------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.xiph.org/pipermail/icecast/attachments/20050626/15e84231/attachment.htm
Michael Smith
2005-Jun-27 04:09 UTC
[Icecast] running icecast and a webserver on same port
On 6/26/05, Justin Bot <justinabomb@gmail.com> wrote:> Care to shed some light on this? I have about 10 IPs that are at my > disposal and 3 I've been keeping for spares and whatnot. Though > binding them is a little beyond me.Just set up your web server on port 80, bound to a specific IP (I don't, offhand, remember how to do this, but it's definately possible), then configure icecast on port 80, bound to a different IP (you can do this by using bind-address set to the IP you wish to use). Mike