[ https://issues.apache.org/jira/browse/TIKA-1461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14188479#comment-14188479 ]
Nick Burch commented on TIKA-1461: ---------------------------------- Do you know the license of that file? And/or of a different jar that is apache / bsd licensed that shows the problem? Before we go about making changes for this, we really want to add a unit test so we can ensure it is properly fixed, but equally importantly remains fixed into the future! > Bad mime detection of certain JAR file > -------------------------------------- > > Key: TIKA-1461 > URL: https://issues.apache.org/jira/browse/TIKA-1461 > Project: Tika > Issue Type: Bug > Components: core > Affects Versions: 1.6 > Reporter: Cservenak, Tamas > > Given this "ordinary" Java JAR file > https://maven.atlassian.com/content/groups/public/com/atlassian/support/healthcheck/support-healthcheck-plugin/1.0.3/support-healthcheck-plugin-1.0.3.jar > Manually inspected and tested it, it is a Jar file and is valid one. > Still, Tika Core's Detector detects it as type {{application/x-msdownload; > format=pe}}. Tthe detection is "hinted" with file name, hence "jar" hint is > present, still it's not detected as desired {{application/java-archive}}. > IMO, this happens due to the problem with priority of > {{application/x-msdownload; format=pe}}, which is 55. If it would be 50, the > "mediation" would kick in, see TIKA-1292. > Changing/overriding magic priority is not possible using > {{custom-mimetypes.xml}} is also not possible. > Unsure what the correct solution is here, nor how to circumvent this without > patching Tika. > The problem affects versions 1.5 but also 1.6, but we target 1.6. -- This message was sent by Atlassian JIRA (v6.3.4#6332)