[ 
https://issues.apache.org/jira/browse/TIKA-3007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16998112#comment-16998112
 ] 

Nick Burch commented on TIKA-3007:
----------------------------------

There is currently no Parser for HEIC files, only mime detection. A basic 
parser has been worked on by a community member, but is still pending a review 
and merge

If you ask Tika to parse the file, it will get routed via the parent-type-known 
rules to the MP4 parser, as there is no HEIC parser yet. That will set a basic 
type as part of its attempts to handle it.

In general, the metadata-based endpoints only return sensible things for 
formats with full parser support. You are hitting a case where there basic 
support for a container format, but not for the specific child format

In almost all cases, if you want to know what a file's type is, call detect. 
(The only one that springs to mind where metadata-based may be better for 
detection is password-protected formats where you know the password)

> Heic images are detected as "application/mp4" when using tika as server
> -----------------------------------------------------------------------
>
>                 Key: TIKA-3007
>                 URL: https://issues.apache.org/jira/browse/TIKA-3007
>             Project: Tika
>          Issue Type: Bug
>          Components: server
>    Affects Versions: 1.23
>            Reporter: Johan
>            Priority: Blocker
>
> Related to https://issues.apache.org/jira/browse/TIKA-2942
> It seems the detection of the heic imags is working for the standalone jar 
> (tika-app-1.23) but not for the server component (tika-server-1.23).
> tika-app-1.23.jar from [https://archive.apache.org/dist/tika/] detects the 
> image with image/heic but it does not work for the server component 
> tika-server-1.23.jar that one returns still "application/mp4". Any clue what 
> might be going wrong? Code has been added only to the tika jar client and not 
> to the server?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to