[
https://issues.apache.org/jira/browse/NIFI-819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15849947#comment-15849947
]
Brandon DeVries commented on NIFI-819:
--------------------------------------
Since InvokeHTTP now works in "standalone" mode and would support this, is this
change to GetHTTP neccessary? InvokeHTTP has some issues / areas of
improvement (e.g. NIFI-3403, NIFI-3402), but do we need to be duplicating
functionality like this? I was actually thinking of suggesting deprecation of
GetHTTP in favor of InvokeHTTP to reduce redundancy...
> 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)
