[ https://issues.apache.org/jira/browse/NIFI-6698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16935288#comment-16935288 ]
Alessandro D'Armiento commented on NIFI-6698: --------------------------------------------- Hello Patrick, I am trying to reproduce the issue, however, when I try to reach [http://localhost:8099/resource?name=ferret&color=purple|http://myserver.com/resource?name=ferret&color=purple:], the generated flowfile seems quite what you were looking for: !image-2019-09-22-15-19-18-523.png! I instead confirm that using the Url encoding (i.e. %26 for the '&' character), the parameters scramble a bit: !image-2019-09-22-15-22-44-053.png! I don't have a CentOS machine to perform the tests. I'm using an Ubuntu 18.04 machine with Nifi 1.9.2 > HandleHttpRequest does not handle multiple URL parameters > --------------------------------------------------------- > > Key: NIFI-6698 > URL: https://issues.apache.org/jira/browse/NIFI-6698 > Project: Apache NiFi > Issue Type: New Feature > Components: Core Framework > Affects Versions: 1.9.2 > Environment: CentOS > Reporter: Patrick Laneville > Priority: Minor > Attachments: image-2019-09-22-15-19-18-523.png, > image-2019-09-22-15-22-44-053.png > > > The http.query.string parameter is updated. However, it is only updated > properly when the URL contains a single parameter. Additional parameters are > truncated when separated by an "&" in the URL. > > Example > Attempt a GET on the following resource: > [http://myserver.com/resource?name=ferret&color=purple:] > Result is the http.query.string attribute in the outgoing flow file is set to > "name=ferret". The problem is the http.query.string should be set to > "name=ferret&color=purple" > However, if you use URL encoding (encode & as %26) and specify > [http://myserver.com/resource?name=ferret%26color=purple|http://myserver.com/resource?name=ferret&color=purple:] > then then http.query.string attribute in the outgoing flow file is set > properly to "name=ferret&color=purple" > However, with the URL encoding work-around the attribute > http.query.param.name is incorrectly set to "ferret&color=purple" -- This message was sent by Atlassian Jira (v8.3.4#803005)