vanity url connection failure

[cj123]

Hi,

The recommended import path mvdan.cc/xurls does not connect.

  ✗ unable to deduce repository and source type for "mvdan.cc/xurls": unable to read metadata: unable to fetch raw metadata: failed HTTP request to URL "http://mvdan.cc/xurls?go-get=1": Get http://mvdan.cc/xurls?go-get=1: dial tcp 178.62.67.243:80: connect: connection refused

I have resolved this by using the link to this github repository.

[mvdan]

Nginx had stopped for some weird reason. It's up again - thanks for reporting.

[sumanthjoel]

Hi,

I am facing the same issue, temporarily solved using github repo.

go get -u mvdan.cc/xurls
package mvdan.cc/xurls: unrecognized import path "mvdan.cc/xurls" (https fetch: Get https://mvdan.cc/xurls?go-get=1: dial tcp 178.62.67.243:443: getsockopt: connection refused)

[mvdan]

Nginx had stopped again - restarted again. I know this is far from ideal, but the internet will be unreliable anyway, so you should be vendoring/caching/mirroring your dependencies.

[cj123]

Really this brings up a question of the necessity/validity of vanity URLs. Your comment on vendoring/caching etc is only valid for “existing” packages. If someone new wants to use your package and nginx is down, that’s a problem.

[mvdan]

That's why the Go team is working on package mirrors and notaries. Vanity URLs actually help with keeping the system working. If GitHub was to disappear in two years (which is entirely possible, see Sourceforge or Google Code), most of the Go packages would need to be renamed, but not mine.