Update mime types with upstream

[adriankirchner]

Pull Request (PR) description

Update default mime types with current upstream at https://github.com/nginx/nginx/blob/3334585539168947650a37d74dd32973ab451d70/conf/mime.types

[puppet-community-rangefinder]

nginx::params is a class

that may have no external impact to Forge modules.

This module is declared in 9 of 578 indexed public Puppetfiles.

---

These results were generated with Rangefinder, a tool that helps predict the downstream impact of breaking changes to elements used in Puppet modules. You can run this on the command line to get a full report.

Exact matches are those that we can positively identify via namespace and the declaring modules' metadata. Non-namespaced items, such as Puppet 3.x functions, will always be reported as near matches only.

[ekohl]

Just a general thought: in RH-based distros there's /etc/mime.types provided by mailcap and on Debian-based there's /etc/mime.types provided by media-types. Can't we just use those rather than having this massive data entry?

[kenyon]

@ekohl I would rather just leave the file alone and use what’s installed by the distribution package, e.g., in nginx-common on Debian.

[ekohl]

Well, that's pretty much my point: do we need to manage this at all?

[adriankirchner]

My guess is that you can't source /etc/mime.types to nginx because of different syntax.

I would rather just leave the file alone and use what’s installed by the distribution package, e.g., in nginx-common on Debian.

That would be fine, but as a user of puppet-nginx I want to be able to add more mime types if necessary