Smart remote capabilities are broken when target Artifactory is running as ROOT (no /artifactory context )

Steps to reproduce:
1. Run 2 Artifactory instances, one of them (A) without /artifactory context. You can use this: https://jfrog.com/knowledge-base/how-do-i-setup-artifactory-to-run-as-the-root-application-in-tomcat/
2. Still in Artifactory A, create a docker remote repository
3. In Artifactory B, create a remote repository and point it to the remote repository from step 2, for example: http://localhost:8081/api/docker/docker-remote
Note the api/docker in order to reproduce this issue.
4. Click on the Test button

The request which will get to Artifactory A is:

20190522175405|1|REQUEST|127.0.0.1|anonymous|GET|/api/api/system/version|HTTP/1.1|404|0

Because Artifactory fails to parse the URL, it ends up with api/api and a 404 error, resulting in no smart remote capabilities for this configuration.

Note: users will still be able to pull images from this repository