[
https://issues.apache.org/jira/browse/NIFI-14304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17931821#comment-17931821
]
ASF subversion and git services commented on NIFI-14304:
--------------------------------------------------------
Commit f8f906d518e0fa83cf7915eb7fc3e1ff3794c8fb in nifi's branch
refs/heads/main from Bob Paulin
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=f8f906d518 ]
NIFI-14304: Improve ElasticSearchClientService HTTP HOST validation.
Signed-off-by: Chris Sampson <[email protected]>
This closes #9756.
> Expand ElasticSearchClientService HTTP HOST Instructions
> --------------------------------------------------------
>
> Key: NIFI-14304
> URL: https://issues.apache.org/jira/browse/NIFI-14304
> Project: Apache NiFi
> Issue Type: Task
> Components: Extensions
> Affects Versions: 2.3.0
> Reporter: Bob Paulin
> Priority: Minor
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The note about HTTP Host that says
> {code:java}
> Note that the Host is included in requests as a header (typically including
> domain and port, e.g. elasticsearch:9200). {code}
> The intent appears to inform the user that the Host header will also be
> modified. However this often this leads the user to specify only host and
> port. This incorrect configuration does trigger a validation message however
> the user is not provided a suggestion of the proper format without reviewing
> the code to see the URI based validation.
> Suggest adding a bit more information to this error to improve the experience.
> EX
> {code:java}
> The HTTP Hosts should be valid URIs including protocol, domain and port for
> each entry.
> For example "https://elasticsearch1:9200,https://elasticsearch2:9200"; {code}
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
