1386648 - Double slash when querying artifact URL results in 404

Status: RESOLVED WONTFIX

(Taskcluster :: Services, defect)

Description

[:gerard-majax]

Attachment: curl -I https://queue.taskcluster.net/v1/task/GksNwUt0S-SzLgErAZ7WGg/runs/0/artifacts/public//deepspeech-0.0.1-cp27-cp27mu-linux_x86_64.whl

STR:
 1. Produce an artifact
 2. Build an URL in shell script and end up with '//'
 3. wget

Expected:
 I guess canonicalization of the URL would get rid of '//'

Actual:
 404.

Example:
 - artifact deepspeech-0.0.1-cp27-cp27mu-linux_x86_64.whl
 - task GksNwUt0S-SzLgErAZ7WGg (will expire in 7 days)
 I built the buggy URL: https://queue.taskcluster.net/v1/task/GksNwUt0S-SzLgErAZ7WGg/runs/0/artifacts/public//deepspeech-0.0.1-cp27-cp27mu-linux_x86_64.whl

Comment 1

[:gerard-majax]

Attachment: curl -I https://queue.taskcluster.net/v1/task/GksNwUt0S-SzLgErAZ7WGg/runs/0/artifacts/public/deepspeech-0.0.1-cp27-cp27mu-linux_x86_64.whl

Comment 2

[:gerard-majax]

It seems that GitHub does not like multiple slashes on gists, but it does on files in repo: https://github.com/taskcluster/generic-worker/blob/master////.taskcluster.yml#L119-L122 or https://github.com/taskcluster////generic-worker////blob/master////.taskcluster.yml#L119-L122

Comment 3

[Dustin J. Mitchell [:dustin] (he/him)]

Fundamentally this comes down to resource naming, and we treat `/` as just part of the resource name -- there's no directory structure here.  So I don't think we should be in the business of canonicalizing `/` characters.