You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Ah, yes. This is coming from Apache, which is (currently) our only source of file extensions. I will need to complete #20 before we can actually have the ability to override the Apache types.
So that references RFC is a draft, so it's not very useful. Apparently it ended up officially becoming audio/vnd.wave in http://tools.ietf.org/html/rfc2361 , but looking around all over the place, it seems like the best choice for us may be to use audio/wav. I haven't determined the reason Apache is using audio/x-wav yet, though.
when setting the mime type for .wav files internet explore is a bit picky...
valid options are: audio/wav, audio/wave, audio/x-wave, audio/vnd.wave
Chrome happily accepts the "audio/x-wav" but IE does not.
See: broofa/mime#118
As broofa points out, "audio/wav" is the official type according to the IANA Waveform Audio File Format registration.
http://tools.ietf.org/html/draft-ema-vpim-wav-00
The text was updated successfully, but these errors were encountered: