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 Thu, 02 Feb 2017 01:50:51 GMT

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

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

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

    https://github.com/apache/nifi/pull/1462#discussion_r99039594
  
    --- Diff: nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/GetHTTP.java
---
    @@ -102,6 +96,11 @@
         + "once the content has been fetched from the given URL, it will not be fetched again
until the content on the remote server changes. Note that due to limitations on state "
         + "management, stored \"last modified\" and etag fields never expire. If the URL
in GetHttp uses Expression Language that is unbounded, there "
         + "is the potential for Out of Memory Errors to occur.")
    +@DynamicProperties({
    +    @DynamicProperty(name = "header_XYZ", value = "The Expression Language to be used
to populate the header value", description = "The additional headers to be sent by the processor
" +
    --- End diff --
    
    fixed


> 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
>             Fix For: 1.2.0
>
>
> 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