nifi-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (NIFI-819) Allow specification of headers for GetHTTP
Date Wed, 01 Feb 2017 23:25:51 GMT

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

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

GitHub user trixpan opened a pull request:

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

    NIFI-819 - Extend GetHTTP to use dynamically produce HTTP headers upo…

    …n a request
    
    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?
    - [x] 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?
    - [x] 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/trixpan/nifi NIFI-819

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

    https://github.com/apache/nifi/pull/1462.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 #1462
    
----
commit 853a83015fd13878d0cc52fc646b2221b15c1443
Author: Andre F de Miranda <trixpan@users.noreply.github.com>
Date:   2017-02-01T23:23:23Z

    NIFI-819 - Extend GetHTTP to use dynamically produce HTTP headers upon a request

----


> Allow specification of headers for GetHTTP
> ------------------------------------------
>
>                 Key: NIFI-819
>                 URL: https://issues.apache.org/jira/browse/NIFI-819
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Extensions
>    Affects Versions: 0.2.1
>            Reporter: Aldrin Piri
>            Assignee: Andre
>            Priority: Minor
>
> There is currently no way to provide additional headers for requests through GetHTTP.
 Some endpoints may require a token or other information to access information.  Currently,
it is possible to work around this with an InvokeHttp driven by a dummy file, but interpretation
of dynamic properties added as additional headers would provide a better option.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message