|Product:||Apache httpd-2||Reporter:||Bradley Farias <bradley.meck>|
|Component:||mod_mime||Assignee:||Apache HTTPD Bugs Mailing List <bugs>|
|OS:||Mac OS X 10.1|
Description Bradley Farias 2017-08-04 16:17:32 UTC
Comment 1 Jacob Champion 2017-08-04 18:46:26 UTC
Thanks for the heads up! Based on those links, I think this needs to be baked a little bit more before we add it to the official mime.types. You've linked to a draft proposal, and IMO it belongs in httpd after it's standardized and/or in wide use. In the meantime, server admins are welcome to adjust the mime.types themselves if they need it, so we're not obstructing the rollout.
Comment 2 Bradley Farias 2017-08-04 19:02:53 UTC
What level of support are you needing. If I move the draft to accepted is that enough? Is the merged PR for node needed if not? This issue is being brought up because it was a web compatiblity concern where people cannot use the same files due to lack of MIME support. Would written statements from browser vendors sway anything?
Comment 3 Jacob Champion 2017-08-04 19:36:38 UTC
Comment 4 Eric Covener 2017-08-05 01:42:21 UTC
Comment 5 Bradley Farias 2020-06-15 20:58:19 UTC
Considering Node 12+ now uses the .mjs MIME publicly and it is present even in WHATWG's HTML specification for clarity https://github.com/whatwg/html/pull/3810 how would I go about bumping this issue?
Comment 6 Bradley Farias 2020-10-20 13:31:38 UTC
The ECMAScript specification itself now has a reference to .mjs https://tc39.es/ecma262/#sec-hostresolveimportedmodule