You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@knox.apache.org by "Kevin Minder (JIRA)" <ji...@apache.org> on 2015/12/22 17:08:46 UTC

[jira] [Updated] (KNOX-618) Rewrite function for accessing header values

     [ https://issues.apache.org/jira/browse/KNOX-618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kevin Minder updated KNOX-618:
------------------------------
    Fix Version/s:     (was: 0.7.0)
                   Future

> Rewrite function for accessing header values
> --------------------------------------------
>
>                 Key: KNOX-618
>                 URL: https://issues.apache.org/jira/browse/KNOX-618
>             Project: Apache Knox
>          Issue Type: New Feature
>          Components: Server
>    Affects Versions: 0.6.0
>            Reporter: Kevin Minder
>            Assignee: Kevin Minder
>            Priority: Minor
>             Fix For: Future
>
>
> I recently ran into a situation where it would have been useful to have access to header values in the rewrite rules.  In particular it would be useful sometimes to API version with a header like this.
> {code}
>     <match pattern="{scheme}://{host}:{port}/api/{path=**}?{**}">
>         <rewrite template=""{scheme}://{host}:{port}/api/{$header[version]}/{path}?{**}""/>
>     </match>
> {code}
> As implied above the rewrite function plugin model seems like an excellent way to provide basic access to header information.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)