This processor is deprecated and may be removed in future releases.
Please consider using one the following alternatives: InvokeHTTP
Please be aware this processor is deprecated and may be removed in the near future. Use InvokeHTTP instead. Performs an HTTP Post with the content of the FlowFile. Uses a connection pool with max number of connections equal to the number of possible endpoints multiplied by the Concurrent Tasks configuration.
http, https, remote, copy, archive
In the list below, the names of required properties appear in bold. Any other properties (not in bold) are considered optional. The table also indicates any default values, and whether a property supports the NiFi Expression Language.
| Display Name | API Name | Default Value | Allowable Values | Description |
|---|---|---|---|---|
| URL | URL | The URL to POST to. The URL may be defined using the Attribute Expression Language. A separate connection pool will be created for each unique host:port combination. Supports Expression Language: true (will be evaluated using flow file attributes and variable registry) | ||
| Max Batch Size | Max Batch Size | 100 MB | If the Send as FlowFile property is true, specifies the max data size for a batch of FlowFiles to send in a single HTTP POST. If not specified, each FlowFile will be sent separately. If the Send as FlowFile property is false, this property is ignored | |
| Max Data to Post per Second | Max Data to Post per Second | The maximum amount of data to send per second; this allows the bandwidth to be throttled to a specified data rate; if not specified, the data rate is not throttled | ||
| SSL Context Service | SSL Context Service | Controller Service API: SSLContextService Implementations: StandardSSLContextService StandardRestrictedSSLContextService | The Controller Service to use in order to obtain an SSL Context | |
| Username | Username | Username required to access the URL | ||
| Password | Password | Password required to access the URL Sensitive Property: true | ||
| Send as FlowFile | Send as FlowFile | false |
| If true, will package the FlowFile's contents and attributes together and send the FlowFile Package; otherwise, will send only the FlowFile's content |
| Use Chunked Encoding | Use Chunked Encoding |
| Specifies whether or not to use Chunked Encoding to send the data. This property is ignored in the event the contents are compressed or sent as FlowFiles. | |
| Compression Level | Compression Level | 0 | Determines the GZIP Compression Level to use when sending the file; the value must be in the range of 0-9. A value of 0 indicates that the file will not be GZIP'ed | |
| Connection Timeout | Connection Timeout | 30 sec | How long to wait when attempting to connect to the remote server before giving up | |
| Data Timeout | Data Timeout | 30 sec | How long to wait between receiving segments of data from the remote server before giving up and discarding the partial file | |
| Attributes to Send as HTTP Headers (Regex) | Attributes to Send as HTTP Headers (Regex) | Specifies the Regular Expression that determines the names of FlowFile attributes that should be sent as HTTP Headers | ||
| User Agent | User Agent | Apache-HttpClient/4.5.14 (Java/1.8.0_422) | What to report as the User Agent when we connect to the remote server | |
| Proxy Configuration Service | proxy-configuration-service | Controller Service API: ProxyConfigurationService Implementation: StandardProxyConfigurationService | Specifies the Proxy Configuration Controller Service to proxy network requests. If set, it supersedes proxy settings configured per component. Supported proxies: HTTP + AuthN | |
| Proxy Host | Proxy Host | The fully qualified hostname or IP address of the proxy server | ||
| Proxy Port | Proxy Port | The port of the proxy server | ||
| Content-Type | Content-Type | ${mime.type} | The Content-Type to specify for the content of the FlowFile being POSTed if Send as FlowFile is false. In the case of an empty value after evaluating an expression language expression, Content-Type defaults to application/octet-stream Supports Expression Language: true (will be evaluated using flow file attributes and variable registry) |
| Name | Description |
|---|---|
| success | Files that are successfully send will be transferred to success |
| failure | Files that fail to send will transferred to failure |