TYPO3 Core

changed it in the AudioTagRenderer to protected $possibleMimeTypes = ['audio/mpeg', 'audio/wav', 'audio/x-wav', 'audio/ogg'];

maybe you wanna review the change in gerrit?

Patch set 2 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/78087

Question is, where does this mime-type come from?

https://mimetype.io/audio/x-wav
says it's deprecated.

Thank you for the additional information which states "you should likely still support it".

As it is needed, it is super easy to implement, it has no side effects and it is recommend it to support it - we should add the mime type to the cms.

Would you mind answering my last question?

Question is, where does this mime-type come from?

What are you doing such that the system identifies a file as audio/x-wav?
Any outdated mime-type detection going on?

I'd like to understand how the problem is rooted.

Question is, where does this mime-type come from?

That´s what the customer told me:

I also looked into where the mime-type comes from (different browsers on Mac and Windows), but couldn't figure out why it's set to x-wav. According to the StackOverflow article, Chrome (or Chromium) and Firefox either set it themselves or the operating system sets it when uploading (I also found x-wav in the Windows registry). I haven't had time to try Linux yet.

Thanks. my question was a bit misleading. The mimetype is usually determined by the server of course. I meant: Which library on the server does the mimetype detection?
I assume this is simply outdated there. I understand, though, that this might not be changeable any time soon.

Note: If the mime-type sent by the client would be trusted, this would be very insecure.

Patch set 1 for branch 11.5 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/78894