JIRA REST API - Actual content encoding does not match response Content-Type

XMLWordPrintable

    • Type: Bug
    • Resolution: Won't Fix
    • Priority: Medium
    • Component/s: Ecosystem
    • None

      NOTE: This bug report is for JIRA Cloud. Using JIRA Server? See the corresponding bug report.

      Jira issues can have non UTF-8 content in summary and description fields.

      When requesting these issues via the Jira REST API, the returned content is non UTF-8 encoded.
      However, the Content-Type response header always specifies the content as 'application/json;charset=UTF-8'

      The Content-Type response header in the REST API should match the actual encoding of the content and vice versa.

              Assignee:
              Unassigned
              Reporter:
              Jordan Drake
              Votes:
              4 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: