[
https://issues.apache.org/jira/browse/NIFI-61?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14996001#comment-14996001
]
Joseph Percivall commented on NIFI-61:
--------------------------------------
I am rolling up a patch now for 1086 but the points I did not get to or are not
valid are below:
- no empty headers: I'm assuming this means don't send dynamic empty http
headers in the call. I didn't include this because empty http headers are
valid.
- user specific dynamic relationships: I did not include this because it is
not needed. Just route on the attribute code afterwards and there are already
enough relationships.
- Configuration option whether the request and/or response is captured and
routed: Did not implement, you can just terminate the relationship.
- Add option to disable remote certificate issues, like invalid hostnames,
etc. Likely install a custom HostnameVerifier to do this: I believe what this
is asking for is fine grain control over the truststore being used. It is
outside the scope of this catch all ticket and I made another ticket:
https://issues.apache.org/jira/browse/NIFI-1129
- Configuration option for the number of files pulled from the queue at a
time: What this is ultimately asking for is a way to reuse connections. This
is a bit different when we use OkHttp vs HttpUrlConnection but ultimately it is
outside the scope of this ticket and I made a ticket for it here:
https://issues.apache.org/jira/browse/NIFI-1130
> Multiple improvements for InvokeHTTP
> ------------------------------------
>
> Key: NIFI-61
> URL: https://issues.apache.org/jira/browse/NIFI-61
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: Joseph Witt
> Priority: Minor
> Fix For: 0.4.0
>
>
> Invoke HTTP should not send empty headers
> InvokeHTTP tx.id not unique across clusters
> Support user dynamic http header properties. A DFM could configure the
> processor to send HTTP headers based on user dynamic properties which are
> dynamic properties which are expression language evaluated. If a user
> specified "User-Agent" as the key and "${user.agent}", this would send the
> user agent from from a flow file attribute.
> support user specific dynamic relationships based on status code
> Provenance enhancements - figure out appropriate provenance strategy. For
> one, we might not want to issue a 'send' event until we know we have had a
> sucessful response from the server (maybe?)
> i.e. Allows a DFM to precisely map any response status code to a defined
> relationship. Include a penalization option for each dynamic relationship.
> A comma seperated list of status codes could be used for the property. For
> example, "Response Code Relationships = 200, 404, 500" Would yield three
> relationships named "200", "400" and "500". Ranges could be useful too, for
> example "200-299" would capture all 2xx responses.
> -- Configuration option for the number of files pulled from the queue at a
> time.
> -- Configuration option whether the request and/or response is captured and
> routed
> -- Configuration option for capturing the repsonse, even for non-2xx
> responses.
> -- Clean up provenance events
> -- Add option to disable remote certificate issues, like invalid hostnames,
> etc. Likely install a custom HostnameVerifier to do this.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
