Icecast - Mar 2005 - Mounting problems...

On Sat, 12 Mar 2005 00:30:58 +1000, Geoff Shang <geoff@hitsandpieces.net>
wrote:
> 
> but it never gets the chance to find out.  Icecast is programmed to provide
> a playlist if you request <mountname>.m3u.  Icecast seems to be
assuming
> that you'd never want to call a mountpoint anything with a .m3u
extension,
> so instead of finding the mount /test.m3u, it's actually looking to
serve a
> .m3u playlist for the /test mountpoint.  Since there is no /test mount, it
> returns 404.
> 
> Bug?  Maybe, maybe not.  Up to the developers to decide I suppose.  On the
> one hand, it's not doing what it probably should do.  On the other
hand,
> you probably shouldn't be doing that anyway.
> 
I think (and I haven't tested it recently, but this is how I designed
it) the /test.m3u request serving a playlist should only happen in
/test is a currently-existing mountpoint. If it isn't, the code will
continue on - and should serve the stream. It probably confuses winamp
and other buggy clients, though.

Mike

On Sat, 12 Mar 2005, Michael Smith wrote:
> I think (and I haven't tested it recently, but this is how I designed
> it) the /test.m3u request serving a playlist should only happen in
> /test is a currently-existing mountpoint.
It doesn't.

<anything>.m3u gets served up a generated .m3u file.

On Sat, 12 Mar 2005 08:27:54 +0000 (UTC), gARetH baBB
<hick.icecast@gink.org> wrote:
> On Sat, 12 Mar 2005, Michael Smith wrote:
> 
> > I think (and I haven't tested it recently, but this is how I
designed
> > it) the /test.m3u request serving a playlist should only happen in
> > /test is a currently-existing mountpoint.
> 
> It doesn't.
> 
> <anything>.m3u gets served up a generated .m3u file.
Yeah. Looks like I misremembered. I guess this is so we can serve m3u
files for other things (e.g. static files).

Mike