Re: [go-nuts] Go import redirect docs are unclear

2024-06-23 Thread 'Axel Wagner' via golang-nuts
The meta tag I gave differs from the meta tag the documentation gave. On Mon, 24 Jun 2024 at 02:50, will@gmail.com wrote: > >Most web servers automatically serve an `index.html` for a request to a > directory. The intent is to use something like that. Though note that you > can also use a fu

Re: [go-nuts] Go import redirect docs are unclear

2024-06-23 Thread will....@gmail.com
>Most web servers automatically serve an `index.html` for a request to a directory. The intent is to use something like that. Though note that you can also use a fuller path: That is, if your git-repo is at `https://code.org/r/exproj` and has import path `example.com/exproj`, you can host a sin

Re: [go-nuts] Go import redirect docs are unclear

2024-06-23 Thread 'Axel Wagner' via golang-nuts
On Sun, 23 Jun 2024 at 16:17, Tobias Klausmann wrote: > Hi! > > On https://pkg.go.dev/cmd/go#hdr-Remote_import_paths, in the section > about using meta tags to redirect from some domain to a known forge, it > says: > > > For example, > > > > `import "example.org/pkg/foo"` > > > > will result in t

[go-nuts] Go import redirect docs are unclear

2024-06-23 Thread Tobias Klausmann
Hi! On https://pkg.go.dev/cmd/go#hdr-Remote_import_paths, in the section about using meta tags to redirect from some domain to a known forge, it says: > For example, > > `import "example.org/pkg/foo"` > > will result in the following requests: > > `https://example.org/pkg/foo?go-get=1` > >