[
https://issues.apache.org/jira/browse/NIFI-201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14259335#comment-14259335
]
ASF GitHub Bot commented on NIFI-201:
-------------------------------------
GitHub user gresockj opened a pull request:
https://github.com/apache/incubator-nifi/pull/7
NIFI-201: Supporting arbitrary HTTP headers as flow file attributes in
ListenHTTP
Implementation for NIFI-201
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gresockj/incubator-nifi NIFI-201
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-nifi/pull/7.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 #7
----
commit b233eaf20d36cd17de9d79a36a4fe3bafe8f99ba
Author: gresockj <[email protected]>
Date: 2014-12-27T03:41:12Z
NIFI-201: Supporting arbitrary HTTP headers as flow file attributes in
ListenHTTP
----
> Support arbitrary headers in ListenHTTP
> ---------------------------------------
>
> Key: NIFI-201
> URL: https://issues.apache.org/jira/browse/NIFI-201
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 0.0.1
> Reporter: Joseph Gresock
> Priority: Minor
> Attachments: ListenHttp_regex_example.xml
>
>
> We'd like ListenHTTP to be able to accept arbitrary HTTP headers to be passed
> along as flow file attributes. This could be analogous to the reverse of
> PostHTTP's "Attributes to Send as HTTP Headers (Regex)" property.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)