Show the port numbers or not on API endpoints when port number is 'standard'

[matthewdarwin]

The readme specifies that port numbers should be specified on API endpoints:

api_endpoint: EOSIO HTTP endpoint http://host:port
ssl_endpoint: EOSIO HTTPS endpoint https://host:port

However, when it is a standard port (80 or 443), the normal convention is to leave it off, when it is the standard port (https://tools.ietf.org/html/rfc3986#section-3.2.3)

So should the readme be amended to follow RFC 3986 convention or we always want the port number?

The validator at https://validate.eosnation.io currently follwows RFC 3986, which is not aligned to the documentation.

[nsjames]

I think for congruency they should be left on. In any case if any user or machine navigates to the url it will strip them but for machines it'll serve as a delimiter for standardized URLs

[blokcrafter-dan]

I think we should follow RFC's when one is available. Here, one is. Drop the port if it's the standard port.