Plugin installation fails for semantically identical webroutes

I’ve noticed if I use:

atlas-plugin-install ... --context-path "/"

Which I believe is default, it fails with a 404 on request:

> HEAD //rest/plugins/1.0/ HTTP/1.1

If I’m explicit with the context path of an empty string ("") then I see success (HEAD /rest/plugins/1.0). This should be considered a bug in bitbucket server, right?