[
https://issues.apache.org/jira/browse/KNOX-711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15317643#comment-15317643
]
Larry McCay commented on KNOX-711:
----------------------------------
So, with the list of configured global services, we have backward compatibility
for wherever things like oozie which may return URLs to other services and
require the rules for other services to fire. At the same time, things like UIs
that have relative paths that may overlap with one another will not impact each
other.
The only time we will need to change this list is when we have a service that
has rule definitions that are needed by another service that gets added to the
stack. This should be extremely infrequent.
It seems like this list is a shortcut for all the rules for a given service
definition.
We be able to override this at the rule level by adding the scope to the
rewrite rule - correct?
> Global Rewrite Rules for a Topology are Problematic
> ---------------------------------------------------
>
> Key: KNOX-711
> URL: https://issues.apache.org/jira/browse/KNOX-711
> Project: Apache Knox
> Issue Type: Bug
> Components: Server
> Reporter: Larry McCay
> Assignee: Sumit Gupta
> Fix For: 0.9.1
>
> Attachments: KNOX_711.patch
>
>
> Due to the fact that the rewrite rules for a topology are global, matching
> patterns that are more generic may cause indeterminate URL rewriting. This is
> more of a problem for proxying UIs than it is for services but since the
> patterns are up to the discretion of the developer they could certainly also
> apply to service definitions.
> For instance, the JOBHISTORY UI rewrite.xml contains a pattern like
> "/static/**". This pattern will match an root relative URLs that start with
> "static". Since other hadoop UIs that may be proxied through the same
> topology will reference similar resources, the URL rewriting may match the
> pattern from the wrong application and interject the service/UI name into the
> URL which will result in 404's.
> This has been observed for the HBase UI when the JOBHISTORY UI is also in the
> same topology.
> The workaround for this issue is to deploy separate topologies for UIs that
> have overlapping matching patterns.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
