[
https://issues.apache.org/jira/browse/KNOX-175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13784162#comment-13784162
]
ASF subversion and git services commented on KNOX-175:
------------------------------------------------------
Commit f7985c7702660c5a761278d6d0419101f1f55cc5 in branch refs/heads/master
from [~darumugam]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-knox.git;h=f7985c7 ]
KNOX-175, support service specific cap for buffering request entities for
replay against WWW-authenticate challenge
> filter order in generated gateway.xml needs to be consistent
> ------------------------------------------------------------
>
> Key: KNOX-175
> URL: https://issues.apache.org/jira/browse/KNOX-175
> Project: Apache Knox
> Issue Type: Bug
> Components: Server
> Affects Versions: 0.3.0
> Reporter: Dilli Arumugam
> Priority: Minor
> Fix For: 0.4.0
>
> Attachments: KNOX-175.patch
>
>
> On reviewing the gateway.xml in the deployed knox webapp, shows filter order
> is not consistent across resources.
> In most of the resources, rewrite filter comes before idenity-assertion
> filter. But, we also see rewrite filer coming after identity-assertion
> filter.
> This could be pointing to a problem in the logic that builds gateway.xml
--
This message was sent by Atlassian JIRA
(v6.1#6144)
