Re: single

I'm not sure but I think Brian changed that between .37 to .39 to being 
enabled by default. So if it is turned on now, and its broken, then 
re-configure mod_mp3 with the feature disabled. =)

I cannot stress enought that the use of content-dispositon should only 
be to fix problems in certain browsers. This does not mean mod_mp3 is 
broken if you have to use this feature. It's one of those situations 
where 90% of the people use a certain brand of browser, and several 
releases of that browser are broken. IE didn't always used to be broken, 
old version of IE4 worked perfectly well, and IE6 appears to work like 
the way IE4 did in regards to content-type, and content-disposition 
issues go.

In general, I think using content-disposition is a good thing for 
mod_mp3 since we have the problem of op=play&file=blahblahblahblhablha 
not ending in .mp3, .pls, or .m3u. As others have pointed out before, 
Windows systems sometimes have to assume the content-type based on the 
notion of a 3 character file name extension. In the situation where 
Windows doesn't have a mapping for the content-type being send by 
apache, and there is not 3 character file extension on the URL, 
content-disposition is the only alternative. The issue always goes back 
to the client side application knowing about mime/content-types 
correctly. Also it is ideal to get away from the url being the 
op=play&file=blah syntax for something rewriten like listen.pls, or 
listen.mp3 dynamically via content-disposition.

Unfourtunatly this is a subject I can rant about forever. Jump in 
#mod_mp3 sometime and we can really hash this out good if you want. =)

-Jon


Bruce M. Walker wrote:

>Damn!  And I had such a good rant going ...
>
>Quoting "Bruce M. Walker" <[email protected]>:
>  
>
>>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.
>>    
>>
>
>
>And this turns out to be untrue: it's *ON* by default (at least in the FreeBSD
>port build), not off--my mistake.  Sorry!
>
>Therefore, you should be seeing Content-disposition headers by default in the
>normal build.  That leaves me wondering why so many Windoze people *still* have
>issues with mod_mp3 playing.
>
>Oh well, a perfectly good excuse to go get a coffee!  :-)
>
>-bmw
>_______________________________________________
>Mod_mp3 mailing list
>[email protected]
>http://lists.tangent.org/mailman/listinfo/mod_mp3
>  
>