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 GitHub Bot (JIRA)" <ji...@apache.org> on 2016/12/29 14:47:58 UTC

[jira] [Commented] (NIFI-3114) Update ListenHTTP processor documentation

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

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

GitHub user pvillard31 opened a pull request:

    https://github.com/apache/nifi/pull/1369

    NIFI-3114 Updated documentation of ListenHTTP

    Thank you for submitting a contribution to Apache NiFi.
    
    In order to streamline the review of the contribution we ask you
    to ensure the following steps have been taken:
    
    ### For all changes:
    - [X] Is there a JIRA ticket associated with this PR? Is it referenced 
         in the commit message?
    
    - [X] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.
    
    - [X] Has your PR been rebased against the latest commit within the target branch (typically master)?
    
    - [X] Is your initial contribution a single, squashed commit?
    
    ### For code changes:
    - [X] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
    - [ ] Have you written or updated unit tests to verify your changes?
    - [ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under [ASF 2.0](http://www.apache.org/legal/resolved.html#category-a)? 
    - [ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
    - [ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
    - [ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?
    
    ### For documentation related changes:
    - [ ] Have you ensured that format looks appropriate for the output in which it is rendered?
    
    ### Note:
    Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/pvillard31/nifi NIFI-3114

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/nifi/pull/1369.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1369
    
----
commit 3abba765ca6332d493ce71154a541d8644b5cdc8
Author: Pierre Villard <pi...@gmail.com>
Date:   2016-12-29T14:46:18Z

    Updated documentation of ListenHTTP

----


> Update ListenHTTP processor documentation
> -----------------------------------------
>
>                 Key: NIFI-3114
>                 URL: https://issues.apache.org/jira/browse/NIFI-3114
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Documentation & Website
>    Affects Versions: 1.1.0
>            Reporter: Andy LoPresto
>              Labels: documentation
>
> The processor documentation for [{{ListenHTTP}}|https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi.processors.standard.ListenHTTP/index.html] describes it as 
> bq. Starts an HTTP Server that is used to receive FlowFiles from remote sources. 
> # the wording implies that users should use this processor for communication between NiFi instances, when [Site to Site|https://nifi.apache.org/docs/nifi-docs/html/user-guide.html#site-to-site] offers a more compelling and robust inter-NiFi communication platform. 
> # the documentation makes no mention that only the {{POST}} and {{HEAD}} HTTP methods are supported, while {{GET}}, {{PUT}}, and {{DELETE}} will result in a error and the HTTP response status code {{405}}. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)