[gopher] Re: Gopher Markup
[Top] [All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
-----BEGIN PGP SIGNED MESSAGE-----
On Wednesday 12 August 2009 13:48 (CEST), Jeroen Schot wrote:
> There is one thing that still confuses me though. The gopher URI scheme says
> nothing about a '/' between the type character and selector string. So both
> gopher://gopher.quux.org/1/Archives and gopher://gopher.quux.org/1Archives are
> valid gopher URI's.
Yes, they are.
> But do these two point to the same resource?
No. One selector is "/Archives", while the other is "Archives". These are NOT
the same selectors, although some (most?) server's implementations will be
tolerant and threat them as the same.
> Both bucktooth
> and pygopherd seem to think so, but I can't find a reference for this in the
Because it's an implementation issue.
You don't even have to use path-like selectors, it's up to the server to decide
what is his selector. A totally valid selector could also look like
Of course, most, if not all, servers are simply using paths as selectors,
because it's the easy way to go, but it's not an obligation of any kind.
You'll find my public OpenPGP key at http://www.viste-family.net/mateusz/pub_key
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
-----END PGP SIGNATURE-----
[gopher] Re: Gopher Markup, Mateusz Viste, 2009/08/11