Uploaded image for project: 'Dev - Nexus Repo'
  1. Dev - Nexus Repo
  2. NEXUS-31088

Helm proxy does not properly handle upstream UTF-8 characters

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 3.32.0, 3.37.3
    • Fix Version/s: None
    • Component/s: helm, Proxy Repository
    • Labels:
    • Notability:
      3

      Description

      If the upstream chart contains UTF-8 characters, Nexus can mishandle these characters in the downstream response.  As a result, the downstream helm client will report:  "error converting YAML to JSON: yaml: invalid trailing UTF-8 octet". 

      Here are some upstream UTF-8 strings -> how they appear proxied through Nexus:
      name: Paul Çab -> name: Paul √áab
      name: Marcy Kłor -> name: Marcy K≈Çor

      The customer reproduced the behavior on 3.32.0-03 and 3.37.3-02

      This issue is reproducible on a Windows machine.  If the file.encoding property is set for the JVM to UTF-8 then it is no longer reproducible. This means the encoding of the file is not set correctly when it is stored into blob storage.

        Attachments

          Activity

            People

            Assignee:
            sshamrai Sergii Shamrai
            Reporter:
            jkruger John Kruger
            CC:
            Anael Latassa
            Last Updated By:
            Sergii Shamrai Sergii Shamrai
            Owner:
            Sergii Shamrai Sergii Shamrai
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:
              Date of First Response:

                tigCommentSecurity.panel-title