code.cloudfoundry.org/clock vanity URL is broken #589
Description
relates to moby/moby#42798
Enter an issue title
The title will be used in the diego-release release notes when the issue is closed.
Start the title with a verb (e.g. Change header styles).
Use the imperative mood in the title (e.g. Fix, not Fixed or Fixes header styles)
code.cloudfoundry.org/clock vanity URL is broken
Summary
The code.cloudfoundry.org/clock vanity URL is broken
Steps to Reproduce
export GOPROXY=direct
go get code.cloudfoundry.org/[email protected]
go get code.cloudfoundry.org/[email protected]: unrecognized import path "code.cloudfoundry.org/clock": https fetch: Get "https://code.cloudfoundry.org/clock?go-get=1": x509: certificate signed by unknown authorityThe URL looks to be redirecting to the documentation, also when ?go-get=1 is set:
curl -v 'https://code.cloudfoundry.org/clock?go-get=1'
* Trying 18.158.32.60:443...
* TCP_NODELAY set
* Connected to code.cloudfoundry.org (18.158.32.60) port 443 (#0)
* ALPN, offering http/1.1
* TLS 1.2 connection using TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
* Server certificate: *.cloudfoundry.org
* Server certificate: R3
* Server certificate: DST Root CA X3
> GET /clock?go-get=1 HTTP/1.1
> Host: code.cloudfoundry.org
> User-Agent: curl/7.65.3
> Accept: */*
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 200 OK
< Server: nginx
< Date: Fri, 27 Aug 2021 23:32:12 GMT
< Content-Type: text/html; charset=utf-8
< Content-Length: 90
< Connection: keep-alive
< Keep-Alive: timeout=20
< X-Vcap-Request-Id: 6f5ff149-5d63-4294-4155-63a4d251e203
<
* Connection #0 to host code.cloudfoundry.org left intact
<meta http-equiv="refresh" content="0; url=https://godoc.org/code.cloudfoundry.org/clock">Diego repo
If the bug is actually in a sub-component of diego-release add the name of the repo here, else, leave blank.
Environment Details
Provide the environment in which Diego is running
- diego-release version or other BOSH releases you have deployed
- any other relevant environmental details
If you include a BOSH deployment manifest or section thereof, make sure to include it in a code block and redact any confidential information such as passwords or private keys.
Possible Causes or Fixes (optional)
If you are familiar with the internals of the Diego system or other CF systems, include any conjectures about the causes of the issue or ways to fix it here.
Additional Text Output, Screenshots, contextual information (optional)
If you have additonal slack conversations, text output, such as logs or stack trace output, or screenshots demonstrating the issue, include them in this section. Please use a code block to preserve multi-line text output or output with leading indentation.