[
https://issues.apache.org/jira/browse/TIKA-1335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14030427#comment-14030427
]
Nick Burch commented on TIKA-1335:
----------------------------------
That's not the right way to trigger detection though, you want `tika --detect
foo.csv`, which will return `text/csv` as expected
The mime type in the header, from the metadata, is set by the parser. Since we
don't have an explicit CSV parser, it gets handled by the default text one
We might want to add a detector endpoint to the JAXRS server, but that'll need
to be a new JIRA!
> mime type for CSV files incorrectly detected as text/plain
> ----------------------------------------------------------
>
> Key: TIKA-1335
> URL: https://issues.apache.org/jira/browse/TIKA-1335
> Project: Tika
> Issue Type: Bug
> Components: mime
> Affects Versions: 1.5, 1.6
> Reporter: Kaijian Xu
> Assignee: Chris A. Mattmann
> Attachments: CDEC_WEATHER_2010_03_02, foo.csv, velocity.csv
>
>
> Mime type autodetection returns "text/plain" for CSV files, for example:
> % tika -m foo.csv
> Content-Encoding: ISO-8859-1
> Content-Length: 78
> Content-Type: text/plain; charset=ISO-8859-1
> resourceName: foo.csv
> This occurs regardless of whether the filename has the appropriate *.csv
> extension or not.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
