jshttp/mime-db

Add mimetype application/x-maff

danny0838 opened this issue · 9 comments

danny0838 commented

Is there currently a protocol for what should be added to custom-types.json and what should not (and instead, be added after registered in IANA)?

dougwilson commented

The protocol is if at all possible nothing should be added there. It should be shrinking in size. It was mainly a mechanism to merge the existing data from the node-mime project and arguing about it is a lot of heart ache when this project should just be aggregating it's upstream sources.

dougwilson commented

Since this module doesn't source the compressible flag (a bad decision, in retrospect) it's the only definately permissible data to add to those files since it's currently the only way to add it.

rmzelle commented

So, should this mimetype be added to custom-types.json? I'd be happy to create a PR to add:

  "application/x-maff": {
    "compressible": false,
    "extensions": ["maff"],
    "sources": [
      "http://maf.mozdev.org/maff-specification.html",
      "https://en.wikipedia.org/wiki/Mozilla_Archive_Format"
    ]
  }
dougwilson commented

Hi @rmzelle the type / extension needs to get added to one of our upstreams: NGINX, Apache, or IANA.

rmzelle commented

In that case this issue can be closed, no?

danny0838 commented

This issue is here for a year. Is there any plan that it should be implemented or not?