You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2020/11/16 11:24:00 UTC
[jira] [Commented] (NIFI-7922) Add support for GET request in
ListenHTTP for health check
[ https://issues.apache.org/jira/browse/NIFI-7922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17232690#comment-17232690 ]
ASF subversion and git services commented on NIFI-7922:
-------------------------------------------------------
Commit e66362194db07798eadb68724072f5e299c65902 in nifi's branch refs/heads/main from Peter Gyori
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=e663621 ]
NIFI-7922: Added support for GET in ListenHTTP for health check
NIFI-7922: Fixes based on review comments
ListenHTTP: changed if(!sslRequired) to if(sslRequired) so that the positive case comes first.
HealthCheckServlet: response body for GET contains "OK".
ContentAcknowledgmentServlet: super.doDelete() is called when a DELETE should be rejected because of port mismatch.
NIFI-7922: Refactored, based on review comments
NIFI-7922: Fixed a checkstyle violation (organized the imports)
This closes #4603.
Signed-off-by: Peter Turcsanyi <tu...@apache.org>
> Add support for GET request in ListenHTTP for health check
> ----------------------------------------------------------
>
> Key: NIFI-7922
> URL: https://issues.apache.org/jira/browse/NIFI-7922
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: Peter Gyori
> Assignee: Peter Gyori
> Priority: Major
> Time Spent: 2h 50m
> Remaining Estimate: 0h
>
> Add support for GET request in ListenHTTP processor, so that when put behind a load balancer, the LB can make a health check to verify that the service is available.
> The health check service should be available on <ListenHTTP_service_URI>/healthcheck.
> It should be available via the listening port specified in the processor's property, but it should optionally be configured to be available on a different port.
> Accessing the health check service via a dedicated port should use 1-way SSL at most, even if the main service uses 2-way SSL, since some load balancers do not support client certificate handling:
> - If the processor is set not to use SSL, SSL should not be used on the health check port, either.
> - If the processor is set to use one-way SSL, one-way SSL should be used on the health check port.
> - If the processor is set to use two-way SSL, one-way SSL should be used on the health check port.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)