Hide Forgot
Description of problem: Creating path based routes with the same hostname is allowed in the same project. So I can create two routes with the same hostname but with different paths pointing to different services. But if I try to create a third route in a different project with the same hostname but a different path I will get a route with the HOST/PORT of the value HostAlreadyClaimed It should not matter if I'm in the same project or different project? As long as the path is different? Version-Release number of selected component (if applicable): 3.2.1 How reproducible: Always Steps to Reproduce: Create a route with hostname and one path in one project and then create a route in different project with the same hostname but with different path Actual results: Expected results: Additional info: Also tested on 3.3 with the same result
https://github.com/openshift/openshift-docs/pull/2886 is already in progress to address that. We do not allow it because it's a security risk. Let's say that namespace A defines: bankofamerica.com path / -> banking app And the login url is: bankofamerica.com/login That will route to the banking app because / matches everything under it. Now let's say namespace B then defines: bankofamerica.com path /login -> hostile app Then they can see all of the credentials that are attempted on bankofamerica.com. While this is heavy-handed and will prevent all logins, and someone likely would notice, there are other clever attacks that one could imagine that would be less obvious.
An enhancement request has been raised to be able to extend the uniqueness check to include path segments: bug 1386243.