[gopher] Gopher standard question

[Kevin Veroneau]

Hello,

  Somebody recently pointed out that they are unable to browse my
Gopherhole using the critically acclaimed web browser elinks.  In the
end, we figure out together it was due to how my gopher server was
sending selectors over to the client.  So, my question, is that is the
proper format of a gophermap type "1" that is sent from the server to
the client?

  To my understanding, the selector is what is suppose to be sent as is
to the host and port on the same line.  This way, services like finger
and CSO work correctly with the Gopher server.

  My server correctly responds the following selector just fine:
echo "sandbox" | nc gopher.veroneau.net 70

  "sandbox" is what the gopher menu has as it's selector for
"Sandbox".  From my understanding of the RFC specs is that there really
is no concept of URIs nor "/", and in fact, the server is free to say
use ":" in place of "/" if it so chooses.  As long as the actual
selectors in the gopher menu are correct.

  The problem with elinks, is that it automatically prepends a "/" to
the selector if it's missing.  To me, this doesn't seem like proper RFC
standard functionality.  Correct me if I'm wrong.

  So, depending on the response, to that the actual standard is for
this, I will either submit a patch to mgod server, or submit a
patch/bug report to elinks.

-- 
Best Regards,
  Kevin Veroneau
  Kevin Veroneau Consulting Services
  kevin at veroneau.net
  https://www.veroneau.net/