You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@knox.apache.org by "David Morin (JIRA)" <ji...@apache.org> on 2018/07/26 19:44:00 UTC

[jira] [Commented] (KNOX-1400) Knox: rewrite for logsearch with a double encoding

    [ https://issues.apache.org/jira/browse/KNOX-1400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16558808#comment-16558808 ] 

David Morin commented on KNOX-1400:
-----------------------------------

PassAllHeadersNoEncodingDispatch didn't work for me.

> Knox: rewrite for logsearch with a double encoding
> --------------------------------------------------
>
>                 Key: KNOX-1400
>                 URL: https://issues.apache.org/jira/browse/KNOX-1400
>             Project: Apache Knox
>          Issue Type: Bug
>          Components: Server
>    Affects Versions: 0.12.0
>            Reporter: David Morin
>            Priority: Major
>              Labels: hdp, knox, logsearch
>         Attachments: rewrite.xml, service.xml
>
>
> Hello,
> I face to some issues with the integration of logsearch with Knox. My cluster is an HDP 2.6.5.
> The Knox version with HDP 2.6.5 is 0.12.0 I've defined the LOGSEARCH topology with custom Xml files but I face to some internal rewrite issues:
> [https://XXXX/gateway/default/logsearch/api/v1/service/logs/histogram?page=0&pageSize=999999999☆tIndex=0&q=*|https://xxxx/gateway/default/logsearch/api/v1/service/logs/histogram?page=0&pageSize=999999999&startIndex=0&q=*]*%*3A*
> [http://XXXX:61888/api/v1/service/logs/histogram?q=*%253A*...|http://xxxx:61888/api/v1/service/logs/histogram?q=*%253A*...] q=_%3A_ replaced by q=_*%25*3A_ => double urlencode.
> Thus logsearch can't handle this kind of request. I'm trying to define a custom dispatch class. The documentation explains a little how to do that but it's not sufficient. I'd like to find a concrete example.
> Where can I find a concrete example of Dispatch class embedded that I can put in a dedicated jar (then I can copy this jar in the ext directory) ? Or how can I handle handle this kind of double encode ?
> Thanks in advance
> Regards,
> David



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)