go-import on non-existent project
Summary
Gitlab responds with valid go-import meta on any random path. With go v1.13 it seems to break go get as it trying to check the parent. I have filled a similar ticket in golang issue tracker as well.
Steps to reproduce
curl "https://gitlab.com/random/xyz/something?go-get=1"
<html><head><meta name="go-import" content="gitlab.com/random/xyz git https://gitlab.com/random/xyz.git" /></head></html>%note: random/xyz/something is really random and doesn't represent any real project.
Example Project
It is not project-specific, but this one was used to demonstrate the issue
What is the current bug behavior?
request to "/random/xyz/something?go-get=1" returns valid go-import meta and it seems to confuse go get
What is the expected correct behavior?
not sure, probably 404, or 400 status