[jira] [Commented] (NIFI-7822) Set raw query string attribute in HandleHttpRequest processor

[Otto Fowler (Jira)]

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

Otto Fowler commented on NIFI-7822:
-----------------------------------

I'm not saying we shouldn't do the raw sting option, just suggesting that we 
implement it such that we don't have multiple copies of things.


> Set raw query string attribute in HandleHttpRequest processor
> -------------------------------------------------------------
>
>                 Key: NIFI-7822
>                 URL: https://issues.apache.org/jira/browse/NIFI-7822
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Extensions
>    Affects Versions: 1.11.4
>            Reporter: Yuriy Flyud
>            Priority: Major
>
> HandleHttpRequest parses a query string and writes output to the following 
> attributes:
>  * http.query.string
>  * http.query.param.XXX
> The problem is that neither of these two options works as expected if I want 
> to use query parameters later in my flow.
> First option holds a DECODED query string, so if we are using some characters 
> like & or = in query parameter names or values - there is no way to resolve 
> this. E.g. query string 'text=abc%26notAProp%3D25' will be decoded to 
> 'text=abc&notAProp=25' which is a completely different query string with 
> additional parameter.
> Second option does not handle duplicating query parameters. So query like 
> 'name=John&name=Colin' will be resolved to a single attribute 'name', with 
> value 'Colin'.
>  
> A simple improvement would be to add an 'http.query.raw.string' at least to 
> give a possibility to parse this query string manually where needed.
> '



--
This message was sent by Atlassian Jira
(v8.3.4#803005)