[
https://issues.apache.org/jira/browse/KNOX-77?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Minder updated KNOX-77:
-----------------------------
Attachment: KNOX-77_1.patch
KNOX-77_1.patch adds support for specifying specific rules to be applied to
specific locations in the request and response. This new capability needs to
be "hooked up" for each service that requires it so this issue remains open.
> Need per-service outbound URL rewriting rules
> ---------------------------------------------
>
> Key: KNOX-77
> URL: https://issues.apache.org/jira/browse/KNOX-77
> Project: Apache Knox
> Issue Type: Bug
> Affects Versions: 0.2.0
> Reporter: Kevin Minder
> Assignee: Kevin Minder
> Priority: Critical
> Fix For: 0.3.0
>
> Attachments: KNOX-77_1.patch
>
>
> For example the HdfsDeploymentContributor outbound rule matches any outbound
> URL and rewrites it to be a DataNode URL. This isn't appropriate. Outbound
> rules might need to be per service or at least allow a particular service to
> select a best match.
> rule = rules.addRule( getRole() + "/" + getName() + "/datanode/outbound" )
> .directions( "outbound" )
> .pattern( "*://*:*/**?**" );
> match = rule.addStep( "match" );
> match.pattern( "*://{host}:{port}/{path=**}?{**}" );
> rewrite = rule.addStep( "rewrite" );
> rewrite.template( CLUSTER_URL_FUNCTION + DATANODE_EXTERNAL_PATH +
> "/{path=**}?{host}&{port}&{**}" );
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
