[ 
https://issues.apache.org/jira/browse/NIFI-4597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16261125#comment-16261125
 ] 

ASF GitHub Bot commented on NIFI-4597:
--------------------------------------

Github user joewitt commented on a diff in the pull request:

    https://github.com/apache/nifi/pull/2266#discussion_r152349436
  
    --- Diff: 
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/ListenHTTP.java
 ---
    @@ -95,6 +95,13 @@
             .expressionLanguageSupported(true)
             .addValidator(StandardValidators.POSITIVE_INTEGER_VALIDATOR)
             .build();
    +    public static final PropertyDescriptor RETURN_CODE = new 
PropertyDescriptor.Builder()
    +            .name("Return Code")
    +            .description("The HTTP return code returned after every HTTP 
call")
    +            .required(true)
    +            .defaultValue("200")
    --- End diff --
    
    Probably should use string value of HttpServletResponse.SC_OK instead of 
"200".  Stays consistent with previous entry used.  Not a big deal at all 
obviously.


> Add a property to override HTTP return code in ListenHTTP processor
> -------------------------------------------------------------------
>
>                 Key: NIFI-4597
>                 URL: https://issues.apache.org/jira/browse/NIFI-4597
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Core Framework
>    Affects Versions: 1.4.0
>            Reporter: Sébastien Bouchex Bellomié
>             Fix For: 1.5.0
>
>
> Current ListenHTTP processor is always returning 200 as HTTP return code but 
> is some case, 204 may be required.
> I know that I may use the HandlerHttpRequest and HandlerHttpResponse couple 
> but that's a bit overkill to this.
> The idea is to have a property (default value is 200) giving the ability to 
> override the return code.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to