Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

.wav files show up as "audio/x-wav" instead of "audio/wav" #22

Closed
LorenzGardner opened this issue Mar 4, 2015 · 2 comments
Closed

.wav files show up as "audio/x-wav" instead of "audio/wav" #22

LorenzGardner opened this issue Mar 4, 2015 · 2 comments
Assignees

Comments

@LorenzGardner
Copy link

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

@dougwilson dougwilson self-assigned this Mar 4, 2015
@dougwilson
Copy link
Contributor

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.

@dougwilson
Copy link
Contributor

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants