rob05c commented on issue #4935: URL: https://github.com/apache/trafficcontrol/issues/4935#issuecomment-669609664
>If the only reason we dropped unique hostnames was to support MSOs, origins should be the only server type that can have non-unique hostnames. We can adjust the constraint for that and re-add the constraint, right? That's not the only reason. That might have been the triggering event, but there are many reasons to support multiple hostnames. It's valid to run a CDN, especialy a small one, with multiple components on the same machine. It's also extremely useful, especially for testing and development, to run multiple caches on the same host on different ports. Fundamentally, hostname does not define a unique server on the internet, host+port does. In fact, it's really FQDN+port (that hasn't been a significant concern in the past, but we should consider including the domain in the key as well). Supporting multiple services in TC on the same host is a very valuable feature we should improve, not remove. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
