Gitlab returns incorrect `meta` tag on `go get` of a repository in a nested namespace

Hi,

We're an EE customer and we've started doing more and more development with Go.

We've noticed that the meta go-import tag response we recieve from gitlab doesn't work with nested namespaces.

For example:

If i go get a repository that's in a root namespace:

morganj@Morgans-MacBook-Pro> curl "https://user:token8@gitlab.internel.co.uk/morganj/ingest/?go-get=1"                      ~
<!DOCTYPE html><html><head><meta content='gitlab.internal.co.uk/morganj/ingest git https://gitlab.internal.co.uk/morganj/ingest.git' name='go-import'></head></html>

However, when I try to access a repository in a nested namespace, it seems to respond with an incorrect meta ta - assuming that the git repository is the one that resides in the root namespace.

morganj@Morgans-MacBook-Pro> curl "https://user:token@gitlab.internal.co.uk/cloud/cloud-engineering/core/?go-get=1"        ~
<!DOCTYPE html><html><head><meta content='gitlab.internal.co.uk/cloud/cloud-engineering git https://gitlab.internal.co.uk/cloud/cloud-engineering.git' name='go-import'></head></html>

It seems to me that this is where the meta tag is generated. But it looks like the response i'm getting doesn't quite fit...

I'm also able to recreate this on gitlab.com:

morganj@Morgans-MacBook-Pro> curl "https://gitlab.com/gogettest1/gogettest2/gogetproject1.git/?go-get=1"       ~
<html><head><meta name="go-import" content="gitlab.com/gogettest1/gogettest2 git https://gitlab.com/gogettest1/gogettest2.git" /></head></html>%

Any suggestions?

Cheers,

Morgan

Edited Jan 21, 2018 by Morgan Jones