[
https://issues.apache.org/jira/browse/NIFI-819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15850022#comment-15850022
]
Aldrin Piri edited comment on NIFI-819 at 2/2/17 3:02 PM:
----------------------------------------------------------
[~devriesb] [~trixpan]
Totally okay with marking this as deprecated but given our release/support
schedule, this would not be a candidate for removal until NiFi 2.0.
Presumably we could tag up Post for deprecation as well with NIFI-1687.
was (Author: aldrin):
[~devriesb] [~trixpan]
Totally okay with marking this as deprecated but given our release/support
schedule, this would not be a candidate for removal until NiFi 2.0.
Presumably we could tag up Post as well with NIFI-1687.
> 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)
