File Manager incorrect type - mime type capitalization issue?

How does the File Manager determine the type ?
The Mime type for jpg appears to be okay.

Code:

# grep -i jpg  /usr/local/apache/conf/mime.types
image/jpeg                                      jpeg jpg jpe

In a browser, looking at a "fancyIndex", the exact same file named as logo.jpg and logo.JPG in both instances shows an image icon as expected.

In File Manager,
logo.jpg shows an image icon and type image/x-generic
logo.JPG shows up incorrectly as text/x-generic however

Mime types are supposed to be case-insensitive.

 

11.54.0.21

 

Back to my original question then - Where is the file manager obtaining this info from ?
Is it reading from mime.types ?
# grep -i jpg /usr/local/apache/conf/mime.types
image/jpeg jpeg jpg jpe

Then presumably, that file needs to have all the capitalized versions of file extensions added in ?
( Despite Apache docs stating = case-insensitive ? )

text/x-c c cc cxx cpp h hh dic

C does not even appear in the mime.types file, so you'd still be getting it wrong per your example.

 

There are not too many applications that differentiate the case of their extensions -are there other common ones than 'C' ? If the file manager is defaulting when it doesn't find the case-sensitive match, could that logic not be changed ?
- check for case-sensitive match -> if not found, default to X

-check for case-sensitive match -> if not found, check for case-insensitive match -> if not found, default to X

Far more people working with files named HTML, JPG, GIF, etc.. than are working with C++; Your mention of c vs C is the first I have ever heard of case being an issue in determining how to treat a file.

[notwithstanding case-sensitivity on most file systems except Windows, but we aren't talking about determining if a file already exists or not.]