[jira] [Commented] (NIFI-10754) Nifi Expression Language method urlEncode does encode a URL path correctly when it contains white space

["Daniel Stieglitz (Jira)" <ji...@apache.org>]

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

Daniel Stieglitz commented on NIFI-10754:
-----------------------------------------

[~exceptionfactory] Would it make sense to have a new Nifi Expression Language method which focuses solely on encoding the URL path?

> Nifi Expression Language method urlEncode does encode a URL path correctly when it contains white space
> -------------------------------------------------------------------------------------------------------
>
>                 Key: NIFI-10754
>                 URL: https://issues.apache.org/jira/browse/NIFI-10754
>             Project: Apache NiFi
>          Issue Type: Bug
>            Reporter: Daniel Stieglitz
>            Priority: Major
>
> The Nifi Expression Language urlEncode method replaces white space with a + and not %20. That is fine for the query section of a URL but not the path. There are many Stackoverflow posts which detail the issue. Here is one, [URLEncoder not able to translate space character|https://stackoverflow.com/questions/4737841/urlencoder-not-able-to-translate-space-character]
> Our particular scenario is where we build a URL from attributes and then try to call the URL with InvokeHTTP
> e.g. of a URL with a space in its path
> {code:java}
> https://somehost/api/v1/somepath /actual?att1=something&att2=somethingelse{code}
> from that URL we only encode the part which may have special characters
> {code:java}
> somepath /actual{code}
> urlEncode will convert that to 
> {code:java}
> somepath+%2Factual{code}
> The + in the URL path is not the same as a blank space hence the call to InvokeHttp fails.



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