Re: MP3DefaultOperation

I suspect what you are seeing is what I encountered, and fixed (with a
contributed patch), months ago.  To test this, try rebuilding mod_mp3.  First,
when you are using configure, specify

  ./configure --with-content_disposition

(or hack the Makefile to define CONTENT_DISPOSITION non-empty.)

Then re-make and reinstall it.

WinAmp used with Netscape or Mozilla doesn't work with mod_mp3 as-is and needs
this option.  The option used to be enabled by default, but was disabled for
reasons unknown.

Good luck!

-bmw


Quoting Tim Wunder <[email protected]>:
> 
> On 6/7/2002 2:19 PM, someone claiming to be Brian Aker wrote:
> > On Fri, 2002-06-07 at 11:11, Tim Wunder wrote:
> > 
> >>So, what am I doing wrong? Is it a server problem, or a client
> problem? 
> > 
> > This is a client problem. Basically you are receiving a file that
> you
> > browser doesn't understand how to deal with. So it is default to
> just
> > trying to save it to disk.
> > 
> > 	-Brian
> 
> OK, let's see if I understand (I'm a little slow, bear with me...).
> mod_mp3 starts sending the stream when a play directive is sent, Mozilla
> sees this and asks me what to do with it. I tell it to use Winamp to
> open it. Mozilla then proceeds to download the file as an MP3, 'cuz
> that's what it thinks it is, to be opened by Winamp after the download
> is finished.
> 
> Now, for fun, I disabled the MP3DefaultOperation and just tried to
> connect Winamp to http://myservername:8000, and it buffers some of the
> stream and then starts playing. So Winamp seems to nkow what to do, but
> Mozilla doesn't. Is there a way to tell Mozilla what to do? I've
> configured Winamp as a Helper App for MIME type audio/mpeg, but Moz
> still wants to download a file before passing the data off to Winamp. I
> guess I gotta read up on interfaces for mod_mp3.
> 
> Thanks, 
> Tim