elsloo opened a new issue #2418: TP - Bypass destination requires protocol URL: https://github.com/apache/trafficcontrol/issues/2418 The current implementation in the portal requires one to specify the protocol on a bypass destination for HTTP delivery services. Traffic Router is written to assume that it is not present, as the old Traffic Ops UI will reject any such configuration, and ensures the field contains FQDN only. Also, while we are at it, we should determine whether this is correct. Perhaps a bypass destination should be allowed to specify HTTP or HTTPS and not rely on the redirection scheme configured on the DS. For sake of argument, consider a delivery service whose redirection scheme is HTTP to HTTPS. The protocol used in the 302 to the bypass destination will be HTTPS. It's entirely possible that we want to redirect to HTTPS on our edge, but keep the bypass over HTTP. There are many examples of these types of scenarios, as we have several redirection schemes. Typically security does not get downgraded from HTTPS to HTTP, so that should be yet another consideration.
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
