[
https://issues.apache.org/jira/browse/NIFI-12842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17821180#comment-17821180
]
WojciechWitos commented on NIFI-12842:
--------------------------------------
[~dstiegli1] The case is that we don't use encoding, it is done by the
processor, where it wasn't done before. We use % in URLS and with this change
impacts our requests.
This applies to % in our case.
!image-2024-02-27-12-09-31-831.png!
!image-2024-02-27-12-10-33-542.png!
And when we try to use encoded %, which is %25, it makes it double
!image-2024-02-27-12-10-59-337.png!
!image-2024-02-27-12-11-39-163.png!
And if we used other signs, it ignored them, like on the screenshot:
!image-2024-02-27-12-12-06-720.png!
!image-2024-02-27-12-13-10-173.png!
And it encoded just % in this case.
Also we would have to change many flows for this case, and also we can't make
other request with ommiting % sign in them.
I think the best case would be to add switch between encode True/False in
processor.
> InvokeHTTP version wrong encoding of % in URL
> ---------------------------------------------
>
> Key: NIFI-12842
> URL: https://issues.apache.org/jira/browse/NIFI-12842
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 1.25.0
> Environment: RHEL 7
> Reporter: WojciechWitos
> Priority: Major
> Attachments: image-2024-02-26-08-10-12-657.png,
> image-2024-02-26-08-11-25-213.png, image-2024-02-26-08-13-14-199.png,
> image-2024-02-26-08-16-36-309.png, image-2024-02-27-12-09-31-831.png,
> image-2024-02-27-12-10-33-542.png, image-2024-02-27-12-10-59-337.png,
> image-2024-02-27-12-11-39-163.png, image-2024-02-27-12-12-00-043.png,
> image-2024-02-27-12-12-06-720.png, image-2024-02-27-12-13-10-173.png
>
>
> Hi!
> I've encountered on the version 1.25 issue with encoding of % in invokehttp
> processor.
> It changes every % into %25, which causes error 403 and most of the flows
> don't work.
> On the version 1.24 everything works properly with this processor.
> Here are the screenshots of 1.25:
> !image-2024-02-26-08-10-12-657.png!
> And request:
> !image-2024-02-26-08-11-25-213.png!
> Where on version 1.24 this issue doesn't persist:
> !image-2024-02-26-08-13-14-199.png!
> !image-2024-02-26-08-16-36-309.png!
> Please investigate this issue, it is the blocker of upgrading the environment
> to this version.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
