[
https://issues.apache.org/jira/browse/NIFI-1133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15012999#comment-15012999
]
ASF subversion and git services commented on NIFI-1133:
-------------------------------------------------------
Commit 8c2323dc8d0e107f1a99898370c7515fa9603122 in nifi's branch
refs/heads/master from [~JPercivall]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=8c2323d ]
NIFI-1086 Provide refactoring of InvokeHTTP
NIFI-980 Add support for HTTP Digest authentication to InvokeHttp
NIFI-1080 Provide additional InvokeHttp unit tests
NIFI-1133 InvokeHTTP Processor does not save Location header for 3xx responses
NIFI-1009 InvokeHTTP should be able to be scheduled without any incoming
connection for GET operations
NIFI-61 Multiple improvements for InvokeHTTP inclusive of providing unique
tx.id across clusters, dynamic HTTP header properties
Signed-off-by: Aldrin Piri <[email protected]>
> InvokeHTTP Processor does not save Location header for 3xx responses
> ---------------------------------------------------------------------
>
> Key: NIFI-1133
> URL: https://issues.apache.org/jira/browse/NIFI-1133
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 0.3.0
> Environment: All
> Reporter: Mans Singh
> Assignee: Joseph Percivall
> Priority: Minor
> Labels: patch
> Fix For: 0.4.0
>
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> InvokeHTTP processor does not save the Location header for 3xx responses. So,
> we can cannot hook up the processor to route based on redirect location
> header values.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
