[jira] [Commented] (NIFI-10754) Add Expression Language method to encode a URI
[ https://issues.apache.org/jira/browse/NIFI-10754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17689936#comment-17689936 ] Daniel Stieglitz commented on NIFI-10754: - [~exceptionfactory] That was it thanks! > Add Expression Language method to encode a URI > -- > > Key: NIFI-10754 > URL: https://issues.apache.org/jira/browse/NIFI-10754 > Project: Apache NiFi > Issue Type: New Feature >Reporter: Daniel Stieglitz >Assignee: Daniel Stieglitz >Priority: Major > Fix For: 1.20.0 > > Time Spent: 3h 10m > Remaining Estimate: 0h > > 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=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)
[jira] [Commented] (NIFI-10754) Add Expression Language method to encode a URI
[ https://issues.apache.org/jira/browse/NIFI-10754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17689919#comment-17689919 ] David Handermann commented on NIFI-10754: - [~dstiegli1] Perhaps you have a cached version? https://nifi.apache.org/docs/nifi-docs/html/expression-language-guide.html#geturi > Add Expression Language method to encode a URI > -- > > Key: NIFI-10754 > URL: https://issues.apache.org/jira/browse/NIFI-10754 > Project: Apache NiFi > Issue Type: New Feature >Reporter: Daniel Stieglitz >Assignee: Daniel Stieglitz >Priority: Major > Fix For: 1.20.0 > > Time Spent: 3h 10m > Remaining Estimate: 0h > > 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=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)
[jira] [Commented] (NIFI-10754) Add Expression Language method to encode a URI
[ https://issues.apache.org/jira/browse/NIFI-10754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17689910#comment-17689910 ] Daniel Stieglitz commented on NIFI-10754: - [~exceptionfactory] I do not see getUri on NIFI Expression Language [documentation page |https://nifi.apache.org/docs/nifi-docs/html/expression-language-guide.html] > Add Expression Language method to encode a URI > -- > > Key: NIFI-10754 > URL: https://issues.apache.org/jira/browse/NIFI-10754 > Project: Apache NiFi > Issue Type: New Feature >Reporter: Daniel Stieglitz >Assignee: Daniel Stieglitz >Priority: Major > Fix For: 1.20.0 > > Time Spent: 3h 10m > Remaining Estimate: 0h > > 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=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)