[
https://issues.apache.org/jira/browse/KNOX-711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumit Gupta updated KNOX-711:
-----------------------------
Attachment: KNOX_711.patch
Patch includes:
1. A new Matcher that picks from various matches based on the scope. The scope
is either the service role or 'global'. A role that is not global is treated as
private to that service i.e. the rule not visible to other services.
2. You can specify a scope in the rewrite rules as well which will be honored.
3. In order to provide ease of use, there is a new config setting where you can
set the list of service names that have global rules. Essentially all services
that are not in this list have rules that are treated as scoped to only to that
service.
The list defaults right now to the REST API services.
> 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)
