Summary

The repository can be cloned using the URL path after the repository have been renamed with a different name.
Restarting Bitbucket Server and clearing the cache does not help.

Steps to Reproduce

Scenario 1

1. Create a repository name original on Bitbucket Server.
2. Perform a clone on the client machine.
3. Rename the repository from original to new on Bitbucket Server.
4. Remove the local repository original on the client machine.
5. Perform the clone for original -> Successful
6. Perform the clone for new -> Successful

Scenario 2

1. Create a repository name original on Bitbucket Server.
2. Rename the repository from original to new on Bitbucket Server.
3. Perform the clone for original -> Successful
4. Perform the clone for new -> Successful

Expected Results

Run in a warning message to indicating the repository does not exist:

$ git clone http://admin@localhost:7990/scm/ren/original.git
Cloning into 'original'...
Password for 'http://admin@localhost:7990': 
fatal: remote error: Repository not found
The requested repository does not exist, or you do not have permission to
access it.

Actual Results

The clone of the renamed repository is successful:

$ git clone http://localhost:7990/scm/ren/original.git
Cloning into 'original'...

Workaround

n/A