On Wed, 28 Feb 2018, Iain R. Learmonth wrote:
With a categorical port you recreate the problems of HTTP where you've broken URLs when you enable TLS. Instead of http://blah/ you now have https://blah/ and these are distinct resources. If you are running two servers, they could have entirely different content and those who have bookmarks/search indexes or anything referencing a URL would find it broken when you enable TLS.
This is not the case when protocol relative URLs are used... Which, BTW, is the way that `lynx -source gopher://some.gopher.server' writes URLs.
see also: https://www.paulirish.com/2010/the-protocol-relative-url/