You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
$ go versiongo version go1.5.1 linux/amd64
# FAILS
$ go get -v bosun.org/cmd/bosun/cacheFetching https://bosun.org/cmd/bosun/cache?go-get=1ignoring https fetch with status code 404Parsing meta tags from https://bosun.org/cmd/bosun/cache?go-get=1 (status code 404)import "bosun.org/cmd/bosun/cache": parsing bosun.org/cmd/bosun/cache: http: read on closed response bodypackage bosun.org/cmd/bosun/cache: unrecognized import path "bosun.org/cmd/bosun/cache"
# WORKS
$ go get -v -insecure bosun.org/cmd/bosun/cacheFetching https://bosun.org/cmd/bosun/cache?go-get=1ignoring https fetch with status code 404Fetching http://bosun.org/cmd/bosun/cache?go-get=1Parsing meta tags from http://bosun.org/cmd/bosun/cache?go-get=1 (status code 404)get "bosun.org/cmd/bosun/cache": found meta tag main.metaImport{Prefix:"bosun.org", VCS:"git", RepoRoot:"https://github.com/bosun-monitor/bosun.git"} at http://bosun.org/cmd/bosun/cache?go-get=1get "bosun.org/cmd/bosun/cache": verifying non-authoritative meta tagFetching https://bosun.org?go-get=1Parsing meta tags from https://bosun.org?go-get=1 (status code 200)bosun.org (download)...
$ curl -s 'https://bosun.org/cmd/bosun/cache?go-get=1'|grep go-import <meta name="go-import" content="bosun.org git https://github.com/bosun-monitor/bosun.git">
Same thing happens with bazil.org/fuse/fs/fstestutil, which is a 404 but with the correct meta tag.
where the expected action would be to parse even a 404 page for meta tags, because that's what the plaintext version does.
If this is not fixed, one cannot easily serve those meta tags from a secure static site; updating the website every time a package is created, just to avoid the 404, is brittle and just unnecessary busywork.
The text was updated successfully, but these errors were encountered:
We host bosun.org on github pages, and there is really no way to serve non 404's without generating a static page for each subpackage we have. Parsing meta tags on 404s would definitely help a lot.
rsc
changed the title
cmd/go: Custom import paths not processed from https resource that 404
cmd/go: custom import paths not processed from https resource that 404
Oct 24, 2015
…sponses
Since we allow non-200 responses from HTTPS in normal operation,
it seems odd to reject them in -insecure operation.
Fixes#13037 (again).
Change-Id: Ie232f7544ab192addfad407525888db6b967befe
Reviewed-on: https://go-review.googlesource.com/17945
Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
Same thing happens with
bazil.org/fuse/fs/fstestutil
, which is a 404 but with the correct meta tag.Looks like an unintended side effect of
where the expected action would be to parse even a 404 page for meta tags, because that's what the plaintext version does.
If this is not fixed, one cannot easily serve those meta tags from a secure static site; updating the website every time a package is created, just to avoid the 404, is brittle and just unnecessary busywork.
The text was updated successfully, but these errors were encountered: