rob05c opened a new issue #4940: URL: https://github.com/apache/trafficcontrol/issues/4940
IP+Port makes much more sense for the Unique Key. The IP+Port is what uniquely defines the server for requests (At the HTTP level, arguably FQDN+Port, but the current key is IP, which is the unique identifier at the IP level). The current IP,Profile setting is undesirable because it makes creating multiple similar servers a huge pain, having to create many duplicate profiles. It also allows for duplicate IP+Port, which should not be allowed. TC should be standardized around either IP+Port or FQDN+Port (possibly both). Labeling 'enhancement' - but this is a on the line of bug, enhancement, and tech debt. ## I'm submitting a ... - improvement request (usability, performance, tech debt, etc.) ## Traffic Control components affected ... - Traffic Ops ## Current behavior: TO Server Unique key is IP+Profile ## Expected / new behavior: TO Server Unique key should be IP+Port. Consider also adding a Domain+Hostname+Port Unique Key. ## Minimal reproduction of the problem with instructions: Try to make 2 servers with the same IP and Profile and different Ports. Observe error. ## Anything else: ---------------------------------------------------------------- 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]
