Uploaded image for project: 'Mender'
  1. Mender
  2. MEN-2082

Artifact download link sent from Mender Server doesn't interpret some letters correctly when it is requested using download artifact APi



    • Type: Bug
    • Status: Rejected
    • Priority: Medium
    • Resolution: Won't Do
    • Affects Version/s: None
    • Fix Version/s: Cleanup-MPPT-2018-11-07
    • Labels:


      This issue occurs when Mender is used as a standalone updater using RPI3. I setuped Mender server 1.4 and I used mender client 1.4 as well. 

      In order to reproduce the issue:

      1- use Mender API 

      2- The obtained response from that APi has the uri and expire attributed inside 

      When deeply looking in the URI, a letter or more could be not correctly interpreted. In my case when I performed the API mentioned in 1, I got the following URI -> 

      https://<My Mender IP Server>:9000/mender-artifact-storage/5f2b9a1c-1e22-4746-ae33-13bfa52bd2f4?X-Amz-Algoender-deployments%2F20180904%2Fus-east-1%2Fs3%2Faws4_request\u0026X-Amz-Date=20180904T092647Z\u0026X-Amz-Expires=900{color:#0000ff}u0026X-Amz-SignedHeaders=host\u0026response-content-type=application%2Fvnd.mender-artifact{color:#0000ff}u0026X-Amz-Signature=440e2b9d97b6d3703eb6930f53c21fd54c5cb5583334a90a0af4c56315e3ae96

      The numbers "\n0026" represents the letter '&'. So in order to access the artifact from the deployment storage using the above generated link from the Mender server, every \n0026 must be replaced with '&'. Only in this case, the above generated link can be used to download the artifact.

      I don't know if this is the only letter which Mender server miss interpret or could it be other letters that may be sent in the URI. 

      Note: This issue only shows up when calling mender from command line not when mender client is used in daemon mode. 

      – For following up exactly my situation I had the following topic on the mender google forum.








            • Assignee:
              mirzak Mirza Krak
              Awad Ahmed Awad
            • Votes:
              0 Vote for this issue
              2 Start watching this issue


              • Created:

                Zendesk Support