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

Sandor Molnar updated KNOX-799:
-------------------------------

+Apache Knox 3.0.0 release preparation+
   
We are about to cut the 3.0.0 release branch. master will move on to 3.1.0.
This issue is currently unresolved and is not automatically included in 3.0.0. 
Please choose one of the following:
# If this belongs in 3.0.0: once the branch is cut, cherry-pick your commit(s) 
onto the new v3.0.0 branch in addition to master. Leave Fix Version = 3.0.0 so 
we can track it.
# Do nothing: we will move this issue to the next release (3.1.0) as part of 
release cleanup.
   
If we don't hear back and see no cherry-pick, the issue will be re-targeted to 
3.1.0. Thanks!

> Rewrite rules for handling of trailing slash '/' 
> -------------------------------------------------
>
>                 Key: KNOX-799
>                 URL: https://issues.apache.org/jira/browse/KNOX-799
>             Project: Apache Knox
>          Issue Type: Bug
>            Reporter: Nishant Bangarwa
>            Priority: Major
>             Fix For: 3.0.0
>
>
> I am trying to use knox as a proxy for superset which is a flask application. 
> Flask applications have behave differently when we add or remove trailing 
> slash in the URL. 
> In superset we have urls both with and without trailing slash and the 
> expected behavior is to keep trailing ‘/‘ if its in the input URL I.e do 
> exact match for the path and substitute it in template including trailing 
> ‘/'. 
> Consider the case of of these two URLs - 
> 1) /users/list/
> 2) /users/add
> Now when I use following rewrite rule - 
> {code}
> <rule dir="IN" name="SUPERSET-UI/superset-ui/inbound/path" 
> pattern="*://*:*/**/superset-ui/{path=**}">
>   <rewrite template="{$serviceUrl[SUPERSET-UI]}/{path=**}"/>
> </rule>
> {code}
> It removes trailing slash from all the matching urls.
> The expected behavior for knox is to preserve trailing '/' in the urls while 
> rewriting. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to