Description:

This processor responds to an HTTP request that was received by the HandleHttpRequest Processor.

The pairing of this Processor with a HandleHttpRequest Processor provides the ability to use NiFi to visually construct a web server that can carry out any functionality that is available through the existing Processors. For example, one could construct a Web-based front end to an SFTP Server by constructing a flow such as:

HandleHttpRequest -> PutSFTP -> HandleHttpResponse

This Processor must be configured with the same <HTTP Context Map> service as the corresponding HandleHttpRequest Processor. Otherwise, all FlowFiles will be routed to the 'failure' relationship.

All FlowFiles must have an attribute named http.context.identifier. The value of this attribute is used to lookup the HTTP Response so that the proper message can be sent back to the requestor. If this attribute is missing, the FlowFile will be routed to 'failure.'

Properties:

In the list below, the names of required properties appear in bold. Any other properties (not in bold) are considered optional. If a property has a default value, it is indicated. If a property supports the use of the NiFi Expression Language (or simply, "expression language"), that is also indicated.

• HTTP Status Code
  • The HTTP Status Code to use when responding to the HTTP Request. See Section 10 of RFC 2616 for more information.
  • Default value: no default
  • Supports expression language: true
• HTTP Context Map
  • The HTTP Context Map Controller Service to use for caching the HTTP Request Information
  • Default value: no default
  • Supports expression language: false

Relationships:

• success
  • If a message is successfully sent back to the requestor, the FlowFile is routed to this relationship.
• failure
  • A FlowFile will be routed to failure under the following conditions:
    • The FlowFile does not have an http.context.identifier attribute
    • The http.context.identifier attribute has a value that cannot be found in the HTTP Context Map
    • The HTTP Status Code is not a number
    • There was a communications failure when attempting to write the response to the requestor

See Also:
HandleHttpRequest
StandardHttpContextMap
StandardSSLContextService