<div dir="auto">I'm not asking a question about how to do a reverseproxy, I'm telling the OP how to do a reverseproxy. I'm not asking any questions about anything.<br><br></div><div style="line-height:1.5"><br><br>-------- Original Message --------<br>Subject: Re: [Icecast] admin console<br>From: Robert Jeffares <jeffares.robert@gmail.com><br>To: icecast@xiph.org<br>CC: <br><br><blockquote style="margin:0 0 0 0.8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>
<p>Hi Jake</p>
<p><a href="http://foo.bar/mountpoint">http://foo.bar/mountpoint</a></p>
<p>is going to be interpreted as port 80 by the player <br />
</p>
<p>You want to do <a href="http://foo.bar:8000/mountpoint">http://foo.bar:8000/mountpoint</a> >
<a href="http://foo.bar/mountpoint">http://foo.bar/mountpoint</a></p>
<p>I think you are going to have to do some port shifting from 8000
> someothernumber like 12345 on the router.</p>
<p>regards</p>
<p>Robert<br />
</p>
<div>On 8/01/20 7:07 pm, <a href="mailto:jake@jakebriggs.com">jake@jakebriggs.com</a>
wrote:<br />
</div>
<blockquote>
<div dir="auto">No I think you misunderstood me. The m3u file
contains the URL with the port number in it, since as far as
icecast knows that's is the URL. It doesn't (and can't) know
that I want a different URL. It has
<a href="http://foo.bar:8000/mountpoint">http://foo.bar:8000/mountpoint</a> but I want
<a href="http://foo.bar/mountpoint">http://foo.bar/mountpoint</a>
<div><br />
</div>
<div>It's the wrong URL from my perspective, which is why I
quoted wrong - I understand it's not wrong, it's just not the
one I want.</div>
<div><br />
</div>
<div>It's got nothing to do with the hostname portion or the
URL. The hostname in both examples (with the port and without
the port) is correct - and identical.</div>
<div><br />
</div>
<div>Jake</div>
<div><br />
</div>
</div>
<div style="line-height:1.5"><br />
<br />
-------- Original Message --------<br />
Subject: Re: [Icecast] admin console<br />
From: Petr Pisar <br />
To: <a href="mailto:icecast@xiph.org">icecast@xiph.org</a><br />
CC: <br />
<br />
<blockquote style="margin:0 0 0 0.8ex;border-left:1px #ccc solid;padding-left:1ex">
<blockquote style="margin:0 0 0 0.8ex;border-left:1px #ccc solid;padding-left:1ex">On Tue,
Jan 07, 2020 at 08:38:41PM +0000, <a href="mailto:jake@jakebriggs.com">jake@jakebriggs.com</a>
wrote:<br />
> January 7, 2020 10:56 AM, "user"
<a href="mailto:5f787a@i2pmail.org"><5f787a@i2pmail.org></a> wrote:<br />
> > 2020-01-06 17:50, Philipp Schafft wrote:<br />
> > <br />
> > I'm consider to put icecast behind reverse
proxy. It is not so easy as I<br />
> > think before. Does anyone have experience with
it?<br />
> <br />
> I run it behind a reverse proxy on apache, and
everything works bar one<br />
> thing - the links in the status and admin interface
that serve up an m3u<br />
> file give you file with the "wrong" URL in it.<br />
> <br />
M3U playlists are (or used to be) typically downloaded by
a web browser and<br />
passed to an external music player. If the M3U playlist
did not contain the<br />
hostname, the music player would see a relative path and
would search the<br />
playlist items in a local file system instead on the
Icecast host. Therefore<br />
Icecast puts its hostname into the playlists.<br />
<br />
-- Petr<br />
<br />
_______________________________________________<br />
Icecast mailing list<br />
<a href="mailto:Icecast@xiph.org">Icecast@xiph.org</a><br />
<a href="http://lists.xiph.org/mailman/listinfo/icecast">http://lists.xiph.org/mailman/listinfo/icecast</a><br />
</blockquote>
</blockquote>
</div>
<br />
<fieldset></fieldset>
<pre>_______________________________________________
Icecast mailing list
<a href="mailto:Icecast@xiph.org">Icecast@xiph.org</a>
<a href="http://lists.xiph.org/mailman/listinfo/icecast">http://lists.xiph.org/mailman/listinfo/icecast</a>
</pre>
</blockquote>
</div>
</blockquote></div>