Dear Web Server Owners,
According to IANA‘s list, you should be using RFC 3003 as a guide. It says your MP3 files should have an MIME type of audio/mpeg
.
It shouldn’t be audio/x-mpeg
, but I can see how that might arise.
It shouldn’t be an empty string – perhaps you are getting confused between MIME and mime?
And it certainly shouldn’t be audio/iTunes
or application/iTunes
. Now, you are just making up crap.
Signed,
One of the many developers, who has to keep adding new fake MIME Types to their whitelists, every time their code falls over.
Comment by Alastair on July 23, 2008
Who uses
audio/iTunes
, orapplication/iTunes
?Name and shame!
Comment by Julian on July 23, 2008
I started getting
application/iTunes
from an NPR server in the last few days.I didn’t record where I saw
audio/iTunes
. Finding out now would require a lot of re-downloading of old files, and it may well have been fixed, so forgive me for not bothering.Comment by Aristotle Pagaltzis on July 23, 2008
Hahaha.
That said, if there is no
Content-Type
header (not a header with an empty value, I mean no header at all), that is acceptable – it means “you are free to sniff the content to determine its type.†It’s not ideal, but neither is it incorrect.Btw, I would bet that whoever made up that crap and capitalised it that way didn’t know they could just as well write it
audio/iTunes
oraudio/itunes
orAUDIO/ITUNES
oraUDiO/iTuNEs
or whatever else. (MIME type names are case-insensitive.)