Uploaded image for project: 'Tika'
  1. Tika
  2. TIKA-974

No longer return charset info in Metadata's CONTENT_ENCODING

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Open
    • Minor
    • Resolution: Unresolved
    • 1.2
    • 2.0.0-BETA, 2.1.0
    • metadata
    • None

    Description

      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

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. TIKA-431 Tika currently misuses the HTTP Content-Encoding header, and does not seem to use the charset part of the Content-Type header properly.

          • Major - Major loss of function.
          • Resolved

          Activity

            People

              Unassigned Unassigned
              kkrugler Kenneth William Krugler
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated: