-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
is there a way to handle different mimetype for same extension #28
Comments
It'd be trivial to extend each function to return an array/slice of MIME types instead of a single one. However, now we have the problem on how to order the types returned, assuming most people are just going to take the first type returned if they only need one. So the first type returned should be the most "correct", but what determines that is going to be inherently arbitrary. As a rule of thumb I would tend to say whichever type was registered with the IANA first unless the later one explicitly supercedes the former, which means |
Source from https://github.com/jshttp/mime-db IANA takes precedence fix abonander#28
The new API I've proposed in this comment will support this: #43 (comment) |
there are some extension has two mimetypes, such as:
rtf application/rtf; text/rtf
sh application/x-sh; text/x-sh
do we have a way to handle such a case or can we customize the buiitin mimetypes?
The text was updated successfully, but these errors were encountered: