Undocumented UMN gopherd feature

--Sig_/RtLCy6_pwQYLJgwugAgOCVH
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

Hi gophers;
I believe I've discovered an undocumented feature of UMN gopherd!
The feature is: A request ending with 0x09 0x2B (tab plus) will be
treated as a Gopher0 request, not a Gopher+ request. I believe the
intent is to indicate Gopher+ support in URLs without breaking
Gopher0 clients; e.g. <gopher://example.com/0/selector%09%2B>. It causes
no overlap because a Gopher+ request will have a mime-type of non-zero
length after the plus-sign.

Did anyone know of this feature? Do any clients / any other servers
implement it?

--Sig_/RtLCy6_pwQYLJgwugAgOCVH
Content-Type: application/pgp-signature
Content-Description: OpenPGP digital signature

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCgAdFiEECRScMMLqbawFEVXLbbTQGyXkVXUFAmXJFxYACgkQbbTQGyXk
VXWB+Qf/cqXUTX/ByXrIY3Pt56rRaRnOTEppDL6Aspo9EqNkR0a1UkkQOzSQepeB
gSON7E817QVq3jJVKIktNSI7lYiNOjMr+lwQCJcW3OZbyYm6TdfQP0ZDUFcqHh8j
9adQprzcBzYR0iMYY1jjerhViT+uf2YpZk88SMLpEbOPcYsy5bw4dnPH1+p31tAG
Ufj1+XPuWoIqSPHSxksHPLV2nPkcckgtjAPDXU+LtOz75r+c+RrOmLCso1egCwIE
5WtfPEfZetC13eB9wGbKi9O5SzaWNyzb1R5GIjIqQwicImxT6EAKj8RCZWIiwUVg
doHwC2dpYi2XdS4TaLOBgEokzRRQ4w==
=Tof0
-----END PGP SIGNATURE-----

--Sig_/RtLCy6_pwQYLJgwugAgOCVH--