Retrieve go-get=1 meta data for a project casing differs based on branch

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

In this section of code for the go.rb library we have a method for returning project paths. We specifically use a different path formation baaed on the depth of the initial request. This "helps" to avoid an issue where a potential malicious user could retrieve path information they should not have.

https://gitlab.com/gitlab-org/gitlab/blob/master/lib/gitlab/middleware/go.rb#L127

Subsequently, it can also remove the casing from the path being used which can break configurations. Is it plausible to resolve these failures by always returning the correct casing for the path of the project?