This RFE is sourced from https://issues.redhat.com/browse/SAT-24731?focusedId=27072723&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-27072723 

Today, a Smart-Proxy has the following URL i.e. https://smart-proxy.example.com:9090 . 

When a client is registered with that smart-proxy, it points to the port 443 of that smart-proxy, i.e. the smart-proxy serves the pulp content over port 443, and the RHSM requests are also accepted on port 443.  

So that is kind of a mismatch of what user can see in-front vs how exactly the individual services like Pulp\RHSM works at the backend. 

Having the format like this can be beneficial for the smart-proxy object:

Name: <user-custom-name>
Hostname: <fqdn|cname>
Satellite-Port: 9090 (default or fixed)
RHSM/Content-port: 443 (default of fixed)

If the Hostname is then changed, it can also update example/references URLs that are generated to give the user feedback on what it means if the hostname is changed or the port has changed perhaps.

But since this cannot be changed at this moment, the request for this Jira is to make sure that the capsule\smart-proxy details page, displays the correct data ( e.g. protocol , name and port a.k.a the URL ) for each of the features e.g. the Pulp and RHSM URLs for content.

Having this transparency would make it visible to the end-users whether the URLs are generated based on the hostname (for the internal capsule) or maybe even from what was generated by the options passed via satellite-installer for CNAME.