[
https://issues.apache.org/jira/browse/TIKA-4172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17789247#comment-17789247
]
martin k. commented on TIKA-4172:
---------------------------------
Thanks [~tilman] for your response.
I spent some time with Tika 2.9.1 now, and I think I found the issue:
{{% curl -T ~/.tmp/d0101c66_mySQL40.sql
[http://localhost:9998/meta/Content-Type]}}
{{Content-Type,application/octet-stream}}
but:
{{% curl -T ~/.tmp/d0101c66_mySQL40.sql -H "Content-Disposition: attachment;
filename=d0101c66_mySQL40.sql" [http://localhost:9998/meta/Content-Type]}}
{{Content-Type,text/x-sql; charset=IBM424}}
So it is the filename that is persuading Tika more than the actual contents. Is
that intentional?
> Apple binary file incorrectly identified as text/x-sql due to filename
> ----------------------------------------------------------------------
>
> Key: TIKA-4172
> URL: https://issues.apache.org/jira/browse/TIKA-4172
> Project: Tika
> Issue Type: Bug
> Components: general
> Affects Versions: 2.9.1
> Reporter: martin k.
> Priority: Minor
>
> This is related to [https://github.com/eikek/docspell/issues/2376] and
> [https://github.com/eikek/docspell/issues/2403.]
> Take the following Base64 encoding of a binary Apple-generated file. No idea
> what it does. You can get the file by piping the following to e.g. {{base64
> -d > something.sql}}
> {code:java}
> ABRkMDEwMWM2Nl9teVNRTDQwLnNxbAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
> AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAbUJJTgAA
> AAAAAAAAAAAAAAAAAACCgf+/AAA=
> {code}
> If this file is name {{{}something.sql{}}}, then Tika will classify it as
> {{{}text/x-sql{}}}, which it is not. It seems like more weight is given to
> the filename (extension) than the fact that the file is binary anyway.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
