Github user dewrich commented on the issue: https://github.com/apache/incubator-trafficcontrol/pull/567 @amiryesh Another feature request Out of curiousity, I configured the gateway to "front" Traffic Ops entirely (and it worked!), but I had to reconfigure the "/login" (which goes to the auth.go) to point to "/jwt_token". Traffic Ops also has a route called "/login", so the mapping had a conflict. Can we build an option to allow for say a prefix mapping such as /traffic_ops so that everytime I request /traffic_ops it removes that from the context before forwarding it to an actual Traffic Ops. This will allow the gateway namespacing to prevent any potential url conflicts. Apache webserver has this feature if you want to research more: Reverse Proxy ProxyPass "/foo" "http://foo.example.com/bar" ProxyPassReverse "/foo" "http://foo.example.com/bar" So the client requests: http://reverse_proxy/foo/bar and the mapping goes to "http://foo.example.com/bar"
--- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---