Page History

...

• HashContent-Migrated.json

InvokeHTTP

Migration

InvokeHTTP includes several deprecated properties for configuring access through a proxy server.

...

• InvokeHTTP-Proxy-Migrated.json

PostHTTP

Alternatives

Migration

PostHTTP supports sending FlowFile content to a configurable HTTP URL using the HTTP POST method.

PostHTTP has a required URL property and also requires an SSL Context Service when the URL indicates an HTTPS location.

PostHTTP supports a specialized mode for transmitting binary packages containing FlowFile attributes and content to the ListenHTTP Processor. This behavior can be enabled using the Send as FlowFile property. There are various approach to implementing similar behavior, including configurable the MergeContent Processor with the FlowFile Version 3 format prior to sending through the InvokeHTTP Processor. Other options include passing selected FlowFile attribute values as HTTP headers, subject to ASCII encoding and length limitations.

The InvokeHTTP Processor supports standard HTTP methods including POST. Unlike PostHTTP, InvokeHTTP does not require an SSL Context Service for accessing HTTPS locations as it defaults to the Java Runtime default certificate authorities.

InvokeHTTP has a required HTTP URL property and also has lower default socket timeout settings than PostHTTP.

Flow Definitions

The Deprecated Flow Definition includes PostHTTP configured to send to ListenHTTP without custom FlowFile binary packaging.

• PostHTTP-Deprecated.json

The Migrated Flow Definition includes InvokeHTTP configured to send to ListenHTTP using equivalent settings.

• PostHTTP-Migrated.json