You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tika.apache.org by "Tyler Palsulich (JIRA)" <ji...@apache.org> on 2015/03/02 23:24:04 UTC

[jira] [Updated] (TIKA-974) No longer return charset info in Metadata's CONTENT_ENCODING

     [ https://issues.apache.org/jira/browse/TIKA-974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tyler Palsulich updated TIKA-974:
---------------------------------
    Fix Version/s: 2.0

> No longer return charset info in Metadata's CONTENT_ENCODING
> ------------------------------------------------------------
>
>                 Key: TIKA-974
>                 URL: https://issues.apache.org/jira/browse/TIKA-974
>             Project: Tika
>          Issue Type: Bug
>          Components: metadata
>    Affects Versions: 1.2
>            Reporter: Ken Krugler
>            Priority: Minor
>             Fix For: 2.0
>
>
> As per TIKA-431, the Content-Encoding field in response headers is used to specify the compression (gzip, deflate, etc) of the response data, not the charset (text encoding).
> Currently Tika returns this from a parse request via Metadata.CONTENT_ENCODING, but that should be deprecated and eventually phased out, e.g. in version 2.0



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)