On Tue, 2005-12-06 at 21:21 +0100, C. Menge wrote: > C. Menge wrote: > > C. Menge wrote: > > > >> [1]: http://stud.uni-karlsruhe.de/~uqc1/temp/content-disposition.jpg > > > > Yikes! Broken link, I apologize. > > > > http://stud.uni-karlsruhe.de/~uqc1/temp/content-disposition.jpg > > > > (note to self: *always* check links before posting...) > > (note again: You stupid moron, do what you write!) > > http://www.stud.uni-karlsruhe.de/~uqc1/temp/content-disposition.jpg
Alright. The content-disposition header isn't specified in RFCs for use in a HTTP header. It is however supported by all major browsers. Firefox and Opera interpret this to be an instruction to download a file rather than an offer. The reason I first sought this was due to XMMS not understanding extended M3U lists without .m3u extensions. This is essentially a bug in XMMS. Info on that can be found here: http://bugs.xmms.org/show_bug.cgi?id=632 I am actually leaning towards removing this extra header. The only time this has played a part has been with custom playlist, and I am thinking about doing some nice things with that plugin :) Yup... remove it :) _______________________________________________ Gnump3d-users mailing list [email protected] http://lists.gnu.org/mailman/listinfo/gnump3d-users
