Re: single

Quoting Jon disnard <[email protected]>:
> 
> You can also use the HTTP content-disposition header to make it work. 
> That header works well with content-name, and content-type headers to 
> work-around the broken IE browser. I think but, I'm not sure, that 
> somebody

Yeah, me. ;-)

> has already hacked together something like that to use the 
> content-disposition header on each request. I'd have to take a look at 
> the configure file to make sure, but I think brian made 
> content-disposition an on/off feature controlled by a configure arg, or
> a directive, or whatever.

No, it's still a compile-time #ifdef ...

   mod_mp3.c: #ifdef CONTENT_DISPOSITION

which you have to know to enable.

I'm afraid I don't understand that feature being an #ifdef that is off by
default, still.  It works and it fixes many (all?) of these PC browser issues. 
I use it regularly, yet I continue to see questions from 1st-time mod_mp3 users
saying, "how come it downloads instead of streaming in my Windows browser?"

I didn't "invent" this method of telling browsers what to do: I observed how
existing websites (eg mp3.com, besonic.de, acidplanet.com, etc.) do it by using
curl and 'lynx -dump' to see what comes down the tubes.  Ever wonder why people
can install IE or NS on Windows, go to these music sites and "it just works
(tm)"?  Then they try mod_mp3, and it doesn't.

I know, "UNIX does it right".  I'm a UNIX guy for crumbs' sake; but when it
comes down to it, what percentage of browsers using mod_mp3 in the future will
be IE compared to all others?  Do the math.

But hey, as long as the code's still there for *me* to enable, guess I can't
complain.  :-)

-bmw