File input give different Mimetype for the same file in chrome or firefox. I have a wav file that I want to upload, chrome says it is audio/wav and firefox detect audio/x-wav.
I know those two mimetype are very similar (x- stands for non-standard), but why are they handled differently in this case?
Here is a fiddle to illustrate this: https://jsfiddle.net/r9ae0zfd/. And here is the WAV file I used for this example: https://freesound.org/people/zagi2/sounds/391828/.
In the end the behavior that I would like is to take a .wav file from my computer (client) and send it by HTTP to my server as audio/wav regardless of the browser.
There's a subsequent question to this: how to harmonize this behavior?