URL schema when written in wrong case fails (not gracefully)

[silverhook]

Describe the bug
When adding a Docker source, the URL schema seems to be case sensitive, and if it is not exactly as docker://, it fails, but does not explain why.

System configuration

• Which version of ScanCode.io are you running? v32.7.0
• Are you running the app using Docker? yes
• On which OS? Linux
• What inputs are you using? docker
• Which pipeline are you running? docker

To Reproduce
Steps to reproduce the behavior:

1. start a new scan
2. add a Docker resource and do a case typo by writing e.g. Docker://postgres:12.17-alpine3.19
3. fill in everything else correctly and set the pipeline to docker
4. start the scan
5. see error

Expected behavior
Either:
a) not have the schema part of the URL case sensitive, and just finish the scan; or
b) return an error, where it explains the issue was the case

[jayanthmahadesh]

when URL is Docker:// instead of docker it raises value error

whitelist = r"^docker://[a-zA-Z0-9_.:/@-]+$"
if not re.match(whitelist, docker_reference):
raise ValueError("Invalid Docker reference.")

should i try
whenever there is case mistake in docker:// - like Docker://
change it to docker:// automatically

[jayanthmahadesh]

@silverhook

[silverhook]

whenever there is case mistake in docker:// - like Docker://
change it to docker:// automatically

That sounds like a great solution, yes. 👍

[jayanth-kumar-morem]

Docker image names, including the part specifying the repository, image name, and tag, are case-insensitive. Therefore, whether you use uppercase or lowercase letters in the image name, repository, or tag, Docker treats them as the same.

For example, both docker://postgres:12.17-alpine3.19 and docker://Postgres:12.17-alpine3.19 refer to the same Docker image.

[tdruez]

Schema validation implemented in #1085

An explicit form error is now displayed for in cases of unsupported scheme: