I’m going to switch my answers to follow what Solderpunk has been saying. The RFCs are pretty clear, as is the w3.org paper on URL parsing at http://www.w3.org/Addressing/URL/4_1_Gopher+.html
If you include a %09 in the URL, the gophertype needs to be a ‘7’. Otherwise, everything past the %09 needs to be stripped from what the client sends.
Thanks to my Azure developer subscription, I’ve just written a small web-search program that looks for every web page (in the first 5000 results) from a Bing web (http) search for “gopher://”. I then grabbed each web page and looked for explicit gopher:// urls.
Obviously this isn’t a complete search (among other things, I’m not including any actual gopher content!). But it is telling that whatever we collectively think is the right thing can be consistent.
My next release of my Gopher client will follow this rule AND will have a UI to get the current page’s gopher URL.
Sent from Mail for Windows 10
(to the list this time, sorry)
> > A URL like gopher://gopher.floodgap.com/0/v2/vs%09cheese (note the 0
> > instead of a 1) will do the search but will treat the results like a file
> > instead of like a directory.
> Again, I would now argue that this URL is invalid since for a type 0
> transaction the client is supposed to send only a selector and a
> selector cannot contain a tab.
I'm not sure I'd agree wit this. A CGI/mole/etc. on the other end may well
want arguments, especially for documents that update dynamically. Is this
in RFC 1436?
------------------------------------ personal: http://www.cameronkaiser.com/ --
Cameron Kaiser * Floodgap Systems * www.floodgap.com * email@example.com
-- Are we not men? We are Klingons! -- Klingon-Devo Mix Masters, Inc. ---------