> I replaced it with application/vnd.adobe.flash.movie, which was > registered in 2013. > > https://www.iana.org/assignments/media-types/application/vnd.adobe.flash.movie > > Sorry that it was not prominently explained in the changelog.
No, it's my bad, the changelog actually stated exactly what was done. I didn't investigate this issue in one time and I must have dismissed and overlooked this new type as not a replacement, on the basis that it was broken for me. I'm getting a crash course here on the different media type components on my system, thanks for clarifying what was intended. > Can you give me details on what is broken by this change ? When opening about:plugins in Firefox, the Flash plugin lists: MIME Type | Description | Suffixes application/x-shockwave-flash | Shockwave Flash | swf application/futuresplash | FutureSplash Player | spl I'm going to surmise that it's the plugin itself that registers which media types it handles; and application/vnd.adobe.flash.movie is not one of them. Consequently, when I open in a new Firefox tab an HTTP URL to an SWF file, if it's served with an application/vnd.adobe.flash.movie HTTP Content-Type header, the Flash plugin doesn't load and I'm prompted to download the file. If it's served with an application/x-shockwave-flash Content-Type, the Flash plugin loads to run the content. As I mentioned, it might also be SWF animations saved on a local drive. So when I open a file:// URL to an SWF file, or use the File > Open dialog, which apparently leads to opening a file:// URL all the same, there is no Content-Type header: and thus I surmise it relies solely on the /etc/mime.types mappings. And opening a file with an .swf extension, prompts me for download with the new application/vnd.adobe.flash.movie mapping, whereas it loads the Flash plugin fine with the old application/x-shockwave-flash mapping. I get the same results over HTTP with no Content-Type. So that's what broken for me. I've tried this an a couple old Firefox versions, because up-to-date versions of major browsers since January now refuse to load and register the Flash plugin altogether, which I've also reported as an offensive issue in itself. I haven't tried any of the alternate products I've mentioned to keep playing Flash content, so I don't know how they handle this; that might be worth checking. It's also unclear to me whether application/vnd.adobe.flash.movie was really registered by an Adobe employee from the Flash maintenance team. Maybe I'm wrong in my analysis of which component would be responsible for handling the media type, but if I'm right, it sure is a shame that the Adobe Flash plugin was never updated to support the registered vendor type; and now it's reached its final version so it's probably unfortunately too late. So considering that the policy is to avoid duplicate mappings, I would suggest reverting .swf to application/x-shockwave-flash, due to lacking support for application/vnd.adobe.flash.movie :/ -- Pierre Ynard
