Joseph Witt created NIFI-61: ------------------------------- Summary: Multiple improvements for InvokeHTTP Key: NIFI-61 URL: https://issues.apache.org/jira/browse/NIFI-61 Project: Apache NiFi Issue Type: Improvement Reporter: Joseph Witt Priority: Minor
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)