[
https://issues.apache.org/jira/browse/NIFI-13810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17885432#comment-17885432
]
ASF subversion and git services commented on NIFI-13810:
--------------------------------------------------------
Commit 6761de3901a36303cd616c69ca05ecc3a1c1127d in nifi's branch
refs/heads/main from David Handermann
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=6761de3901 ]
NIFI-13810 Handled Trailing Separator for Paths in URI Builder
This closes #9319.
Signed-off-by: Peter Turcsanyi <[email protected]>
> StandardHttpUriBuilder should handle optional ending / (slash) in base paths
> ----------------------------------------------------------------------------
>
> Key: NIFI-13810
> URL: https://issues.apache.org/jira/browse/NIFI-13810
> Project: Apache NiFi
> Issue Type: Bug
> Reporter: Peter Turcsanyi
> Assignee: David Handermann
> Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> NIFI-13619 swithced the HTTP client implementation under
> StandardWebClientService and StandardHttpUriBuilder from OkHttp to Java
> built-in.
> The old OkHttp-based implementation handled the ending / (slash) character in
> base paths as optional (add if not present, do not duplicate if present).
> The new version requires an explicit / (slash) at the end of the base path
> otherwise the URL will be invalid when additional path segments are added to
> the base path.
> StandardHttpUriBuilder should provide the old behaviour and handle base paths
> w/o ending / (slash).
> Affected components using StandardHttpUriBuilder with base path + path
> segments: QueryAirtable, SlackRecordSink
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
