mime.types parsing and commas

[Brian Behlendorf <br...@organic.com>]

I dunno if this is a bug or not, but I had one entry in my mime.types 
file that used a "," to separate multiple file name extensions for a 
given mime type, when the norm is to use a space, and whereas apache 
0.6.5 accepted that fine 0.8.10 didn't (resulting in mpeg audio files 
typed as text/plain :)  I don't know what the standard is for mime.types 
files - I don't even know if there is a standard - but it's yet another 
behavior change, even though it's exceedingly minor.  It's only worth 
fixing if the mime.types "spec" if one exists allows commas as file 
separators.

	Brian

--=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=--
brian@organic.com  brian@hyperreal.com  http://www.[hyperreal,organic].com/

Re: mime.types parsing and commas

[Alexei Kosut <ak...@nueva.pvt.k12.ca.us>]

On Sun, 20 Aug 1995, Brian Behlendorf wrote:

> I dunno if this is a bug or not, but I had one entry in my mime.types 
> file that used a "," to separate multiple file name extensions for a 
> given mime type, when the norm is to use a space, and whereas apache 
> 0.6.5 accepted that fine 0.8.10 didn't (resulting in mpeg audio files 
> typed as text/plain :)  I don't know what the standard is for mime.types 
> files - I don't even know if there is a standard - but it's yet another 
> behavior change, even though it's exceedingly minor.  It's only worth 
> fixing if the mime.types "spec" if one exists allows commas as file 
> separators.

Spec? Well, I think the closest that comes to that is 
http://hoohoo.ncsa.uiuc.edu/docs/setup/httpd/TypesConfig.html, which 
defines the format of the mime.types file for NCSA httpd, and makes no 
mention of commas, only spaces.

--/ Alexei Kosut <ak...@nueva.pvt.k12.ca.us> /--------/ Lefler on IRC
----------------------------/ <http://www.nueva.pvt.k12.ca.us/~akosut/>
The viewpoints expressed above are entirely false, and in no way
represent Alexei Kosut nor any other person or entity. /--------------