On Mon Jul 31 08:12:43 2023 +0000, Rémi Bernon wrote:
Actually I'm not even sure this is very useful. The scheme resolver also sets the `MF_BYTESTREAM_CONTENT_TYPE` attributes on Windows (although to `audio/x-wav`), which will be enough to not require `MF_RESOLUTION_CONTENT_DOES_NOT_HAVE_TO_MATCH_EXTENSION_OR_MIME_TYPE`. On Wine we will miss the content type until we have a better implementation of http scheme handlers with access to the response headers.
I've added a generic `MF_BYTESTREAM_CONTENT_TYPE` instead.