rob05c commented on issue #3537: URL: https://github.com/apache/trafficcontrol/issues/3537#issuecomment-1307560241
> So when we move from parent.config to strategies.yaml, duplicate origins won't be a problem anymore, different remaps (Delivery Services) can map to the same parent without issues. I was wrong about this. Strategies fixes the problem with origins. But ATC child–parent cache communication uses (non-CONNECT) forward proxying. Which means remaps from children are matched via the origin FQDN. So strategies fixes half the problem, config around parent.config. But for DSes using parent caches, all config will arbitrarily be one of the two DSes, including cache key, header rewrites, and basically all other config. I think the only way to fix that is going to be to move away from true Forward Proxying, and start using artificial FQDNs for child–parent communication and remaps. -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
