Rest API: Wrong UTF8 Data

XMLWordPrintable

    • Severity 3 - Minor
    • Hide

      Atlassian Update – 04 July 2019

      Hi everyone,

      After reviewing the overall customer interest and impact of this bug report we have decided to close this issue down. Our analysis has shown that over time this issue hasn't collected a significant number of votes, watchers, comments, or support cases from customers and therefore has remained very low on our priority list. Given these findings we can conclude it will not be fixed in the foreseeable future and wish to be transparent about our priorities by closing it as Timed Out.

      Although we're aware this issue may be still important to those of you who were involved in the initial conversations around it, we want to be clear by managing your expectations regarding the likelihood of a fix for it. The Jira team do their best to prioritise the issues that have high and critical impact with broad pervasiveness reflected in series of different factors. You can learn more about this by reading our Bug Fixing Policy.

      To see what the Jira team is currently working on and has recently delivered see the following dashboards:

      We understand that hearing a decision like this can be disappointing, but we hope you'll appreciate our transparent approach to product priorities and communications. We will continue to watch this issue for further updates, so please feel free to share any thoughts in the comments.

      Thank you,

      Pawel Drygas,

      Jira Server Bugmaster

      Show
      Atlassian Update – 04 July 2019 Hi everyone, After reviewing the overall customer interest and impact of this bug report we have decided to close this issue down. Our analysis has shown that over time this issue hasn't collected a significant number of votes, watchers, comments, or support cases from customers and therefore has remained very low on our priority list. Given these findings we can conclude it will not be fixed in the foreseeable future and wish to be transparent about our priorities by closing it as Timed Out . Although we're aware this issue may be still important to those of you who were involved in the initial conversations around it, we want to be clear by managing your expectations regarding the likelihood of a fix for it. The Jira team do their best to prioritise the issues that have high and critical impact with broad pervasiveness reflected in series of different factors. You can learn more about this by reading our Bug Fixing Policy . To see what the Jira team is currently working on and has recently delivered see the following dashboards: Jira Server and Data Center: Recently resolved issues Jira Server and Data Center: Current work and future plans Jira Server and Data Center: Bug Fix Board We understand that hearing a decision like this can be disappointing, but we hope you'll appreciate our transparent approach to product priorities and communications. We will continue to watch this issue for further updates, so please feel free to share any thoughts in the comments. Thank you, Pawel Drygas, Jira Server Bugmaster

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

      I found a bug within the rest API while we were testing our interface to JIRA, fetching issues from JIRA.

      After creating an issue with 5000 'ä' we get a python error on our side:

      UnicodeDecodeError: 'utf8' codec can't decode bytes in position 8197-8198: invalid data

      Usually this means encoding is set wrong, but in this case, JIRA sends wrong UTF8 Data.

      \xc3\xa4 stands for 'ä' in the utf-8 encoding tab. After 3779 of \xc3\xa4 JIRA adds some extra bytes '\r\nb2c\r\n'.This cuts through the byte of \xc3 and \xa4 making the data unreadable causing the decode error.

      Problem does not exist with 3000 'ä'

        1. bytestring.txt
          40 kB
          Ramon Clematide
        2. data_chunk.png
          13 kB
          Ramon Clematide

            Assignee:
            Unassigned
            Reporter:
            Ramon Clematide
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: