You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tika.apache.org by "Adrien Nguyen (Jira)" <ji...@apache.org> on 2022/07/26 14:12:00 UTC

[jira] [Commented] (TIKA-1997) Problem in Tika().detect for xml file signed in CADES

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

Adrien Nguyen commented on TIKA-1997:
-------------------------------------

[~NguyenKhacChinh] [~roberto.benedetti] 

I see that the config file also specifies <glob pattern="*.p7s"/> for pkcs7-signature and <glob pattern="*.dbf"/><glob pattern="*.dbase"/> <glob pattern="*.dbase3"/> for application/x-dbf

If the filename had the correct extension, would it be a higher priority then the magic value ?

Is there a way to change that priority or disable application/x-dbf entirely in our own app ?

> Problem in Tika().detect for xml file signed in CADES
> -----------------------------------------------------
>
>                 Key: TIKA-1997
>                 URL: https://issues.apache.org/jira/browse/TIKA-1997
>             Project: Tika
>          Issue Type: Sub-task
>          Components: detector
>    Affects Versions: 1.13
>         Environment: JDK 1.7
>            Reporter: Michele Andreano
>            Priority: Blocker
>         Attachments: test.xml.p7m
>
>
> When I submit a tika a xml file signed in P7M format, I expect tika return as mimetype application / pkcs7-mime instead gives me application / pkcs7-signature.
> How is it possible?



--
This message was sent by Atlassian Jira
(v8.20.10#820010)